Security Resilience

CVE-2024-0039

Memory Safety in Google Android 12.0 … 14.0

Published
11 March 2024
Modified
13 March 2025
Patch / advisory
CVSS Score v3.1 9.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.015 74th percentile
Risk Priority 85 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2024-0039 is a critical-severity Out-of-bounds Write (CWE-787) vulnerability in Google Android. Its CVSS base score is 9.8 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Security Account Manager (T1003.002); ranked in the top 26% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2024-0039 is an out-of-bounds write in the function attp_build_value_cmd within att_protocol.cc of the Android Bluetooth module. The flaw stems from a missing bounds check and is tracked under CWE-787. It affects the Bluetooth stack in Android and carries a CVSS 3.1 score of 9.8.

An unauthenticated remote attacker can trigger the vulnerability over the network without user interaction or additional privileges, resulting in remote code execution on the target device. The attack surface is exposed whenever Bluetooth is enabled and processing incoming attribute protocol commands.

Public patches addressing the issue appear in the Android Open Source Project commits referenced in the March 2024 Android security bulletin, which back-port bounds checks to the affected Bluetooth code paths.

EPSS for the CVE rose from lower values to a peak of 0.2625 on 2025-12-11 before receding to the current 0.1964, indicating measurable post-disclosure exploitation interest.

EU & UK References

Vulnerability Data

In attp_build_value_cmd of att_protocol.cc, there is a possible out of bounds write due to a missing bounds check. This could lead to remote code execution with no additional execution privileges needed. User interaction is not needed for exploitation.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1003.002 Security Account Manager Credential Access
Adversaries may attempt to extract credential material from the Security Account Manager (SAM) database either through in-memory techniques or through the Windows Registry where the SAM database is stored.
T1003.004 LSA Secrets Credential Access
Adversaries with SYSTEM access to a host may attempt to access Local Security Authority (LSA) secrets, which can contain a variety of different credential materials, such as credentials for service accounts.
T1003.008 /etc/passwd and /etc/shadow Credential Access
Adversaries may attempt to dump the contents of <code>/etc/passwd</code> and <code>/etc/shadow</code> to enable offline password cracking.
T1006 Direct Volume Access Stealth
Adversaries may directly access a volume to bypass file access controls and file system monitoring.
T1007 System Service Discovery Discovery
Adversaries may try to gather information about registered local system services.
T1012 Query Registry Discovery
Adversaries may interact with the Windows Registry to gather information about the system, configuration, and installed software.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-40091Same product: Google Android
CVE-2024-23709Same product: Google Android
CVE-2024-31336Same product: Google Android
CVE-2024-23698Same product: Google Android
CVE-2023-40110Same product: Google Android
CVE-2024-32909Same product: Google Android
CVE-2023-21250Same product: Google Android
CVE-2024-29749Same product: Google Android
CVE-2023-48403Same product: Google Android
CVE-2023-45775Same product: Google Android

Affected Assets

google
android
12.0, 12.1, 13.0, 14.0

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation (including fuzzing and bounds checks) finds out-of-bounds write flaws before deployment.

Requiring documented secure-development standards and tools can mandate bounds-checked coding practices that avoid the weakness.

Input validation can structurally reject or sanitize data that would otherwise trigger an out-of-bounds write.

Memory-protection mechanisms limit the exploitability and blast radius of a successful out-of-bounds write.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

ID.RA-01 partial match
blocks

Vulnerability scanning and recording can discover out-of-bounds write flaws so they can be remediated.

PR.PS-02 partial match
blocks

Patching or replacing vulnerable software directly eliminates known instances of this coding weakness.

PR.PS-06 partial match
blocks

Secure-development practices (static analysis, bounds checking, code review) are the primary means of preventing out-of-bounds writes.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

removes
removes
removes
removes
removes

References