dbcve.org
AndroidOperating system · Google

CVE-2024-29751

MEDIUM · 5.5 CVSS v3.1 Published 2024-04-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In asn1_ec_pkey_parse_p384 of asn1_common.c, there is a possible OOB Read due to a missing null check. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A missing null check in the asn1_ec_pkey_parse_p384 function in asn1_common.c causes an out-of-bounds read when parsing ASN.1 encoded EC P-384 keys. This can lead to disclosure of sensitive information from memory to a local attacker without requiring any special privileges or user interaction.

MitigationAdd a null check for the parsed key data pointer before dereferencing in the asn1_ec_pkey_parse_p384 function to prevent the OOB read. Ensure proper bounds validation is performed throughout the ASN.1 parsing logic.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
AndroidOperating system
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm the target device runs Google Android
    Check the operating system by reviewing system properties or /system/build.prop for 'ro.build.fingerprint' containing 'Android'
    Affected if The device does not run Google Android, the vulnerability does not apply
  2. Identify if ASN.1 EC key parsing is in use
    Review application logs or network traffic for operations involving EC P-384 keys (look for 'secp384r1' or 'ECDSA P-384' in cryptographic operations)
    Affected if No EC P-384 key parsing operations occur, the vulnerable code path is not triggered
  3. Check for the vulnerable asn1_common.c component
    Examine the system library responsible for ASN.1 parsing (typically part of the platform security library or boringssl) for the presence of the asn1_ec_pkey_parse_p384 function
    Affected if The function exists in the ASN.1 parsing library on the device, the vulnerable code is present
  4. Determine if applications process external ASN.1 encoded EC keys
    Audit installed applications for those that accept or parse ASN.1 encoded EC keys from untrusted sources (check app permissions and input handling for key import features)
    Affected if Applications process external ASN.1 encoded EC P-384 keys, the out-of-bounds read can be triggered

If the device runs Google Android and applications process ASN.1 encoded EC P-384 keys from external sources, the environment is affected by this vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Add a null check for the parsed key data pointer before dereferencing in the asn1_ec_pkey_parse_p384 function to prevent the OOB read. Ensure proper bounds validation is performed throughout the ASN.1 parsing logic.

Recommended fix Moderate confidence

Latest Android security patch level (March 2024 or later, depending on device manufacturer)

  1. 1. Navigate to Settings > Security & Privacy on the Android device
  2. 2. Select 'Security Update' or 'System Update'
  3. 3. Check for and install the latest Android security patch update
  4. 4. Ensure the device is running the latest available Android version for your device model
  5. 5. After updating, verify the patch level by going to Settings > About Phone > Android Version or Build Number to confirm the security patch level is current (typically March 2024 or later for this CVE)
Caveat Risk is minimal for security updates; some older devices may not receive further updates and may need replacement

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Android Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-29751 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-29751 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data