CVE-2024-20011
Published: 05 February 2024
Summary
CVE-2024-20011 is a critical-severity Improper Restriction of Operations within the Bounds of a Memory Buffer (CWE-119) vulnerability in Google Android. Its CVSS base score is 9.8 (Critical).
Operationally, ranked in the top 9.0% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
Deeper analysis
In the ALAC decoder, an incorrect bounds check creates a vulnerability that can result in information disclosure and potentially remote code execution. The issue is tracked as CVE-2024-20011 with a CVSS score of 9.8 and is associated with CWE-119. It affects MediaTek components that incorporate the ALAC decoder, as indicated by the Patch ID and Issue ID ALPS08441146.
An unauthenticated attacker can exploit the flaw over the network without user interaction or additional privileges. Successful exploitation grants the ability to disclose sensitive information and achieve remote code execution, which carries high impact across confidentiality, integrity, and availability.
MediaTek's February 2024 product security bulletin references the same Patch ID ALPS08441146 as the fix for this issue. The EPSS score has remained flat at 0.0615 with no material increase since disclosure.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-17726
Vulnerability details
In alac decoder, there is a possible information disclosure due to an incorrect bounds check. This could lead to remote code execution with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS08441146; Issue ID:…
more
ALPS08441146.
- CWE(s)
Related Threats
No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Ongoing control assessments and code testing (static/dynamic analysis, fuzzing) surface memory buffer restriction failures, which are then remediated before release.
Managed runtimes used by platform-independent applications (e.g., JVM, CLR) enforce memory safety, preventing most buffer overflows that require direct memory manipulation.
Memory protections (e.g., W^X, ASLR) make exploitation of buffer-boundary violations far harder to turn into code execution.
Detects exploitation attempts that produce memory corruption, crashes, or anomalous behavior.