dbcve.org
AndroidOperating system · Google

CVE-2024-29780

MEDIUM · 5.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 →
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 hwbcc_ns_deprivilege of trusty/user/base/lib/hwbcc/client/hwbcc.c, there is a possible uninitialized stack data disclosure due to uninitialized data. 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

In the Trusty Trusted Execution Environment (TEE) hwbcc client library, the hwbcc_ns_deprivilege function in hwbcc.c contains a vulnerability where uninitialized stack data may be disclosed to a local attacker. This occurs because a stack variable is used without being properly initialized, potentially leaking sensitive memory contents to an unprivileged local user.

MitigationThe fix requires initializing all stack variables in the hwbcc_ns_deprivilege function before use. Since this is Trusty TEE code, the patch must be delivered through firmware/TEE updates from the device manufacturer, which can be challenging to deploy across the Android ecosystem.

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 if the Android device has Trusty Trusted Execution Environment by reviewing device specifications, manufacturer documentation, or using 'getprop ro.trusty.version' in ADB shell if available
    Affected if Device does not have Trusty TEE or the property returns no value, the vulnerability does not apply
  2. Check hwbcc client library presence
    Search for the hwbcc library in the Trusty TEE firmware image or system分区 if you have root access and can extract firmware
    Affected if hwbcc library is present and the device runs any version of Android, the function hwbcc_ns_deprivilege in hwbcc.c may contain the uninitialized stack variable
  3. Verify uninitialized stack variable in hwbcc.c
    If you can obtain the Trusty TEE binary/source, inspect the hwbcc_ns_deprivilege function in hwbcc.c for stack variables used without initialization
    Affected if The function contains stack variables declared but not initialized before use, indicating the vulnerability is present
  4. Check manufacturer firmware version
    Consult the device manufacturer's security bulletin or contact them to determine the Trusty TEE firmware version installed
    Affected if The installed TEE firmware version predates the security patch that initializes stack variables in hwbcc_ns_deprivilege

A user is affected if their Android device runs Trusty TEE with the hwbcc client library containing uninitialized stack variable in the hwbcc_ns_deprivilege function, which requires checking manufacturer documentation or firmware analysis since TEE internals are not directly accessible from userland.

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

The fix requires initializing all stack variables in the hwbcc_ns_deprivilege function before use. Since this is Trusty TEE code, the patch must be delivered through firmware/TEE updates from the device manufacturer, which can be challenging to deploy across the Android ecosystem.

Recommended fix Moderate confidence

Android Security Patch Level containing the CVE-2024-29780 fix (check source.android.com security bulletins for the specific release date)

  1. 1. Wait for the monthly Android Security Bulletin that includes this CVE (CVE-2024-29780) and apply the corresponding Android Security Patch Level update from your device manufacturer.
  2. 2. Ensure your Android device is set to receive and install system updates automatically, or manually check for updates in Settings > System > Software Update.
  3. 3. After the patch is applied, verify the Android Security Patch Level in Settings > About Phone > Android Security Patch Level matches or exceeds the bulletin date containing 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
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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