dbcve.org
AndroidOperating system · Google

CVE-2024-29757

HIGH · 7.3 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 →
75/100
Remediation priority · High
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
there is a possible permission bypass due to Debug certs being allowlisted. This could lead to local escalation of privilege 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 · moderate confidence

This is a permission bypass vulnerability where debug certificates are incorrectly allowlisted in a system's trust store. Since debug certificates are trusted for authentication/authorization, an attacker with local access can use these certificates to escalate privileges to a higher permission level without requiring any user interaction or additional execution privileges.

MitigationRemove debug/development certificates from production allowlists and implement proper certificate validation that only trusts production-issued certificates. Verify that all debug certificates are revoked or removed from production environments.

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
High
Availability
Low

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

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. Identify trusted system certificates
    On the Android device, navigate to Settings > Security & privacy > Encryption & credentials > Trusted certificates. On root-accessible devices, also check /system/etc/security/cacerts/ for CA certificates installed at the system level.
    Affected if Any certificate in the system trust store is a known debug, development, or test certificate that was issued for development purposes rather than production use.
  2. Inspect certificate details for debug markers
    Review each certificate in the system trust store. Look for certificates with subjects, issuers, or serial numbers indicating they are debug keys, such as those containing 'debug', 'test', 'development', or 'Android' in the certificate subject/issuer fields.
    Affected if A certificate in the trust store is identified as a debug or development certificate, meaning it was generated for testing purposes and should not be trusted in production.
  3. Check for Android platform debug keys
    On rooted devices or through system inspection, verify if the Android platform signing key (typically found in build/target/product/security/ during development) is present in the system trust store or trusted for system-level authentication.
    Affected if Any certificate corresponding to the Android platform debug signing key is present in or trusted by the system certificate store.
  4. Review sideloaded or preinstalled certificates
    Check for certificates installed via device manufacturer preloading, carrier bundles, or enterprise management that may contain development or test certificates. Use 'settings list global' or check /data/misc/user/0/cacerts-added/ for added certificates.
    Affected if Any certificate was added to the trust store that originated from a development or debug certificate authority rather than a production CA.

The environment is affected if any debug, development, test, or Android platform signing certificates are present in the system trust store or are incorrectly trusted for authentication/authorization purposes.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Remove debug/development certificates from production allowlists and implement proper certificate validation that only trusts production-issued certificates. Verify that all debug certificates are revoked or removed from production environments.

Fix this in Android Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA5.0 h
31.0 hours of engineering $5,460
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-29757 — 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-29757 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