Unauthenticated code execution via MFC heap overflow
Published Mar 11, 2024 · Updated Aug 28, 2024
Heap out-of-bounds write in the MFC component of Google Android 13 allows remote attackers to execute code over a network. The bulletin identifies MFC as the affected subcomponent, but its private issue record withholds the function and input path that overrun the heap buffer. Exploitation requires no privileges or user interaction and runs attacker-controlled code on an affected Pixel device.
Summary
What happened
Heap out-of-bounds write in the MFC component of Google Android 13 allows remote attackers to execute code over a network. The bulletin identifies MFC as the affected subcomponent, but its private issue record withholds the function and input path that overrun the heap buffer. Exploitation requires no privileges or user interaction and runs attacker-controlled code on an affected Pixel device.
The record
- CVE
- CVE-2024-27228
- Published
- Mar 11, 2024
- Updated
- Aug 28, 2024
- Vendor
- Product
- Android
- Classifications
- CWE-787
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 11, 2024CVE publishedPublication date reported by the CVE source.
- Aug 28, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=13
- Affected versionversion=13.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
No public exploit references are available in this record.
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