An app crashes the system that is supposed to inspect it. Does your review record the incident, or does it simply mark the job as failed?
Bitdefender found GhostMap after an Android package crashed its analysis emulators during installation. The researchers went on to demonstrate a separate, more disruptive outcome: a specially crafted app could leave a test phone repeatedly restarting, even though the app contained no executable code and requested no permissions. Recovery could require a factory reset. In their 5 November report, the researchers said they had not observed attackers using the persistent crash loop against victims.
For an organisation distributing Android apps, a failed inspection belongs in the approval record. Keep the package identifier and version, the test environment and the point at which inspection stopped. Have the review team investigate the failure in an isolated environment before making a distribution decision.
Check that the release process distinguishes a completed scan from a scan that returned no result. An app owner needs to know which of those outcomes they are being asked to accept.
Source
Read the original GhostMap investigation from Bitdefender Labs
