dbcve.org
AndroidOperating system · Google

CVE-2024-47029

MEDIUM · 5.5 CVSS v3.1 Published 2024-10-25
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 TrustySharedMemoryManager::GetSharedMemory of ondevice/trusty/trusty_shared_memory_manager.cc, there is a possible out of bounds read due to an incorrect bounds 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 · moderate confidence

An out-of-bounds read vulnerability exists in TrustySharedMemoryManager::GetSharedMemory due to an incorrect bounds check in the Trusty secure OS shared memory manager. This allows local information disclosure by reading beyond allocated memory boundaries without requiring any elevated privileges or user interaction.

MitigationApply the Trusty OS firmware update containing the corrected bounds check in trusty_shared_memory_manager.cc; contact the device or SoC manufacturer for patched firmware.

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 device uses Trusty TEE
    Check /proc/tee/ or /sys/class/misc/tee* for Trusty device nodes, or use 'getprop ro.hardware.trusty' to check if the device has Trusty enabled
    Affected if Device does not have Trusty TEE present or enabled, as the vulnerability exists in Trusty secure OS shared memory manager
  2. Identify Android patch level
    Run 'getprop ro.build.version.security_patch' or check Settings > About Phone > Android security patch level
    Affected if Patch level is earlier than the Google Android Security Bulletin release date for CVE-2024-47029, as all prior versions contain the vulnerable bounds check in trusty_shared_memory_manager.cc
  3. Check Trusty firmware version if exposed
    Query device-specific Trusty version via 'dmesg | grep -i trusty' or vendor-specific diagnostic tools if available; some devices expose TEE version through /sys/class/tui/tui_version or similar
    Affected if Trusty firmware version predates the security fix for the bounds check in TrustySharedMemoryManager::GetSharedMemory
  4. Verify shared memory manager is in use
    Check for active Trusty apps or services that utilize shared memory: review Trusty kernel module loading or look for trusty-ipc drivers loaded via 'lsmod | grep trusty' or 'cat /proc/modules | grep trusty'
    Affected if Shared memory manager component is active and the Trusty version is unpatched, enabling the out-of-bounds read condition
  5. Confirm no custom TEE隔离
    Verify the device is not using an alternative TEE implementation (like OP-TEE or Qualcomm TEE) instead of Trusty by checking 'getprop ro.hardware' or /sys/class/tty/ for TEE driver information
    Affected if Device uses Trusty as its primary TEE and the vulnerability is present; devices with non-Trusty TEEs may not be affected by this specific Trusty vulnerability

If the device runs Android with Trusty TEE enabled and has a security patch level predating the CVE-2024-47029 fix, the out-of-bounds read in TrustySharedMemoryManager::GetSharedMemory is present and could allow local information disclosure beyond shared memory boundaries.

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

Apply the Trusty OS firmware update containing the corrected bounds check in trusty_shared_memory_manager.cc; contact the device or SoC manufacturer for patched firmware.

Fix this in Android Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,120
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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