CVE-2024-23355
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 · uneditedMemory corruption when keymaster operation imports a shared key.
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 confidenceMemory corruption vulnerability in Android's keymaster subsystem when importing a shared key. The bug occurs in the key import operation path, allowing local attackers to corrupt memory, potentially leading to code execution or privilege escalation within the TEE or keymaster context.
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 dataall versionsall versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS 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
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Identify the chipset modelCheck the system-on-chip (SoC) model by reading /proc/cpuinfo, /sys/class/socinfo, or using 'lshw' or 'cat /proc/device-tree/model' on the Android device. Look specifically for one of: WSA8845h, WSA8845, WSA8840, WSA8835, WSA8830, WSA8815, WSA8810, or WCN3988.Affected if The device uses any of the listed Qualcomm chipset models (WSA8845h, WSA8845, WSA8840, WSA8835, WSA8830, WSA8815, WSA8810, WCN3988).
-
Verify keymaster HAL service presenceCheck if the keymaster hardware abstraction layer is running on the device by examining running services: 'dumpsys | grep -i keymaster' or checking /vendor/etc/init/android.hardware.keymaster* service definitions.Affected if The keymaster HAL service is present and running on the device, indicating the vulnerable subsystem is active.
-
Confirm shared key import functionality is accessibleReview keymaster configuration files in /vendor/etc/ or /system/etc/ for key import operation enablement. Check keymaster HAL logs for any key import related operations using 'logcat | grep -i keymaster'.Affected if Key import operations (KeyImport or related keymaster commands) are logged or the key import feature is enabled in the keymaster HAL configuration.
-
Check vendor security advisory statusConsult the device vendor's security bulletin or patch documentation for CVE-2024-23355. Cross-reference the firmware version with the vendor's published patch status.Affected if The device firmware has not received a vendor patch addressing CVE-2024-23355, or the vendor has not issued a security advisory confirming the fix.
A user is affected if their Android device contains any of the listed Qualcomm chipsets (WSA8845h through WCN3988) and the keymaster subsystem is active, unless a vendor-specific security patch for CVE-2024-23355 has been applied.
Generated from the published advisory. Verify against your own configuration.
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 dataApply vendor-specific security patches for Android systems supporting keymaster. Ensure keymaster HAL implementations properly validate key import parameters and bounds-check all key material before copying into allocated buffers.
- Consultation8.0 h
- Implementation24.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-23355 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-23355 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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