dbcve.org
AndroidOperating system · Google

CVE-2024-29781

HIGH · 7.5 CVSS v3.1 Published 2024-06-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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 ss_AnalyzeOssReturnResUssdArgIe of ss_OssAsnManagement.c, there is a possible out of bounds read due to improper input validation. This could lead to remote 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

An out-of-bounds read vulnerability exists in the ss_AnalyzeOssReturnResUssdArgIe function within ss_OssAsnManagement.c due to improper input validation. The vulnerability allows remote attackers to read memory contents beyond allocated buffers, leading to information disclosure. No privileges or user interaction are required for exploitation.

MitigationApply a patch or update that adds proper bounds checking and input validation in the ss_AnalyzeOssReturnResUssdArgIe function to prevent out-of-bounds memory reads during ASN.1 parsing of USSD arguments.

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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. Check Android version and security patch level
    Go to Settings > About Phone > Android version and Build number. Alternatively, run 'getprop ro.build.version.release' and 'getprop ro.build.version.security_patch' via ADB
    Affected if The device is running any version of Android that has not received the CVE-2024-29781 patch (typically before the May 2024 Android Security Patch Level)
  2. Verify USSD handling is enabled
    Check if the device can handle USSD codes. Open the Phone dialer and attempt to dial a USSD code (like *#123#). Also verify 'Settings > Network & Internet > Calls > USSD' settings are accessible
    Affected if USSD functionality is present and the ss_AnalyzeOssReturnResUssdArgIe function processes incoming USSD arguments from the cellular network
  3. Check telephony RIL version
    Run 'getprop | grep -i ril' or 'getprop radio.version' via ADB to check the Radio Interface Layer (RIL) or modem firmware version
    Affected if The RIL daemon (rild) or modem firmware contains the vulnerable ss_OssAsnManagement.c code without the bounds checking fix
  4. Inspect telephony service logs
    Run 'logcat -d | grep -i ussd' or 'logcat -d | grep ss_AnalyzeOss' via ADB to check for USSD-related operations
    Affected if USSD messages are being processed by the ss_AnalyzeOssReturnResUssdArgIe function, which is where the out-of-bounds read occurs

A user is affected if the device runs Android and processes incoming USSD messages from the cellular network, unless the May 2024 or later Android Security Patch has been applied.

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

Apply a patch or update that adds proper bounds checking and input validation in the ss_AnalyzeOssReturnResUssdArgIe function to prevent out-of-bounds memory reads during ASN.1 parsing of USSD arguments.

Recommended fix Moderate confidence

Android Security Patch Level containing the CVE-2024-29781 fix (check Android Security Bulletin for specific month)

  1. 1. Check the Android Security Bulletin for CVE-2024-29781 to identify the specific Android Security Patch Level that contains the fix.
  2. 2. Apply the monthly Android security update that includes the patch for this vulnerability to your Android device.
  3. 3. If you are a device manufacturer or build Android from source, locate the patch for ss_OssAsnManagement.c in the Android upstream code repository and apply the fix to your build.
  4. 4. Verify the device shows the Android Security Patch Level that includes the fix for this CVE.

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

Fix this in Android Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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