GhostMap Android Flaw Can Trigger Persistent Crash Loops From a Crafted App

· Original article ↗

Summary

Bitdefender researchers detail GhostMap, an Android ZIP-parsing flaw that can make a crafted app trigger a persistent system crash loop, potentially requiring a data-erasing reset. Reproduced on Android 10+; no in-the-wild use observed, and Google says no security fix.

Key points

  • Researchers say libziparchive and libandroidfw handle ZIP compression methods differently, allowing a malformed entry's declared size to cause an oversized memory mapping and SIGBUS when read.
  • Installing a crafted app can trigger crashes without the app being opened, requesting permissions, or containing executable code; a malformed resource can make system_server repeatedly crash and restart.
  • Rebooting and safe mode do not stop the demonstrated crash loop. Recovery may require a factory reset, which erases local data; ADB may help only in limited conditions.
  • Bitdefender reports reproducing the issue on a Pixel 10 running Android 17 and on Android versions from 10 onward.
  • The investigation began with a banking dropper sample that crashed during installation. Researchers say it only caused a failed install and found no indication its author intended the crash.
  • Researchers say they have not observed the persistent crash-loop scenario used against anyone. Google considered the issue outside the scope of a security update and referred it to a team for possible future consideration.
  • Bitdefender says its mobile product detects the malformed files, but Android does not let third-party apps block installation or remove another app automatically.

Article Details

Attack Vectors
  • A malformed APK contains a ZIP entry whose compression method is neither stored nor deflated and whose declared uncompressed length exceeds the file. When Android parses or reads the entry, the resulting out-of-bounds mapping can cause a SIGBUS and crash the reading process.
  • The malformed manifest can crash the installer during installation; the wild-collected sample caused this failure, but the article says there is no evidence its author intended it.
  • In a demonstrated scenario, a malformed resource read automatically by a core Android service crashes system_server repeatedly, preventing the phone from completing startup. The researchers say they have not seen this used against anyone.
  • Hypothetically, a malicious app could malform its icon so that launcher and settings screens crash when opened, obstructing its removal.
  • A malformed APK can crash Android-based security scanners or analysis tools when they parse it. Researchers reproduced a crash in an ordinary app using the standard APK-parsing API.
  • The researchers describe introducing a malformed file through a later app update as a theoretical delivery scenario, not an observed attack.
Defensive Notes
  • The article reports that no fix was available as of publication and that Google considered the issue outside the scope of a security update, referring it for possible consideration in a future version.
  • The malformed file can be identified by inspecting its structure without installing or running the app.
  • Bitdefender reports that Bitdefender Mobile Security detects the malformation in downloaded and installed apps; a user must act on the warning because Android does not let a third-party app block installation or remove another app on its own.
  • If the phone enters the demonstrated crash loop, the researchers say a factory reset may be required and erases locally stored data. ADB-based deletion may work only in limited circumstances, including having Developer Mode enabled beforehand.

MITRE ATT&CK

CVE

Malware

Vendors

Products

Tools

Related Articles