APK code substitution via inconsistent ZIP header lengths
Published Jan 23, 2020 · Updated Aug 6, 2024
Signature verification bypass in Google Android before 4.4 allows attackers to alter an APK without invalidating its original signature. ZipFile reads a file-name length from the central directory while other parsers use the local header, so conflicting lengths expose different bytes to verification and execution. A crafted APK must reach an affected device; substituted code retains the original package signature and associated trust.
Summary
What happened
Signature verification bypass in Google Android before 4.4 allows attackers to alter an APK without invalidating its original signature. ZipFile reads a file-name length from the central directory while other parsers use the local header, so conflicting lengths expose different bytes to verification and execution. A crafted APK must reach an affected device; substituted code retains the original package signature and associated trust.
The record
- CVE
- CVE-2013-6792
- Published
- Jan 23, 2020
- Updated
- Aug 6, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1036
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 23, 2020CVE publishedPublication date reported by the CVE source.
- Aug 6, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Google Android - Signature Verification Security Bypassfunctional · validated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo