Qué ocurrió
Bitdefender researchers found that two Android libraries interpret ZIP compression methods inconsistently. A specially crafted APK can bypass size checks, map a file into an unallocated memory region, and cause the core system_server process to read invalid memory, raising a SIGBUS and crashing. The crash triggers an automatic restart, leading to a persistent boot loop that repeats over 100 times on a Pixel 10 with Android 17. The malicious app requires no permissions and does not need to be launched. Google has been aware since August 2024 but has not released a patch, classifying the report as “not reproducible.”
Por qué es importante para la confianza y el cumplimiento
- The flaw demonstrates why organizations must maintain continuous vulnerability‑identification and remediation processes that cover third‑party components, a control area that maps to many frameworks such as NIST CSF 2.0.
- Incorporate library‑level flaws into your vulnerability‑management evidence collection.
- Demonstrate to auditors that you have a process for tracking and remediating OS‑vendor‑reported issues.
Who is affected
Mobile device manufacturers Enterprise MDM providers Organizations deploying Android devices
Recommended actions
- Create an inventory of Android versions in use and flag those with the vulnerable libraries.
- Add this vulnerability class to your continuous monitoring and patch‑tracking workflow.
- Update incident‑response playbooks to include boot‑loop recovery steps.