dbcve.org
AndroidOperating system · Google

CVE-2024-32920

HIGH · 7.1 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 →
73/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 set_secure_reg of sac_handler.c, there is a possible out of bounds read due to a missing bounds check. This could lead to local information disclosure of 4 bytes of stack memory 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 bounds check in the set_secure_reg function of sac_handler.c allows an out-of-bounds read of 4 bytes from the stack. This occurs when the code accesses memory beyond the allocated buffer without validating the index or size against the buffer boundaries, exposing sensitive stack memory contents to a local attacker without requiring elevated privileges or user interaction.

MitigationImplement proper bounds validation before array/buffer access in set_secure_reg to ensure the read index stays within allocated buffer limits. Validate all size parameters and buffer boundaries before performing memory reads.

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
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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/build.prop or using 'getprop ro.build.id' to verify Android is the OS
    Affected if The device does not run Google Android OS (this CVE only affects Android)
  2. Identify the Android build version
    Run 'getprop ro.build.version.release' to determine the Android version number
    Affected if All Android versions are affected per the CVE advisory - there is no safe version range
  3. Locate the sac_handler component
    Search for files named 'sac_handler.c', 'sac_handler', or 'libsac' in /vendor, /system, or /boot partitions using 'find / -name '*sac_handler*' 2>/dev/null'
    Affected if The vulnerable set_secure_reg function exists in this component; if present and running on Android, the device is potentially affected
  4. Verify secure boot or TEE is enabled
    Check if the device has a Trusted Execution Environment (TEE) or secure boot by examining /proc/tee/info or using 'getprop ro.tee' if available
    Affected if The vulnerable set_secure_reg function operates within the TEE/secure boot context; devices with TEE enabled that contain the vulnerable sac_handler component are affected
  5. Check for the set_secure_reg function in system binaries
    Use 'strings' or 'grep' to search for 'set_secure_reg' in /vendor/firmware or /system/bin/* binaries: 'strings /vendor/firmware/* 2>/dev/null | grep set_secure_reg'
    Affected if The presence of this function confirms the vulnerable code path exists on the device

Since all Google Android versions are affected and the vulnerability is in a specific function (set_secure_reg in sac_handler.c), a device is affected if it runs any version of Android and contains the vulnerable component with the out-of-bounds read capability.

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

Implement proper bounds validation before array/buffer access in set_secure_reg to ensure the read index stays within allocated buffer limits. Validate all size parameters and buffer boundaries before performing memory reads.

Recommended fix Moderate confidence

Android Security Patch Level 2024-06-01 or later (verify exact patch level in official Android Security Bulletin)

  1. Check the Android Security Bulletin for the month when CVE-2024-32920 was addressed to identify the specific patch level containing the fix
  2. Apply the latest Android security patch level for your device. Navigate to Settings > Security > Security update and ensure the patch level includes the fix for this CVE
  3. For devices with older patch levels, contact your device manufacturer (OEM) to obtain the security update that addresses CVE-2024-32920
  4. If no update is available from your OEM, consider migrating to a device that receives regular security updates or a custom ROM that includes the fix

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

Fix this in Android Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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