CVE-2023-24850
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 in HLOS while importing a cryptographic key into KeyMaster Trusted Application.
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 the KeyMaster Trusted Application occurring during cryptographic key import operations on the HLOS (High-Level Operating System). This flaw could potentially allow a local attacker to corrupt memory via specially crafted key import operations, possibly leading to key extraction or code execution within the trusted execution environment.
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 Qualcomm chip modelCheck the device or system information to determine the exact Qualcomm chip in use (e.g., via 'lspci', 'cat /proc/cpuinfo', or system firmware/dmesg).Affected if The chip model matches one of the affected variants: Apq8017, Apq8037, Aqt1000, Ar8035, Csra6620, Csra6640, Fastconnect 6200, or Fastconnect 6700.
-
Verify KeyMaster Trusted Application is presentCheck for the KeyMaster TA (Trusted Application) in the TEE environment. This may be visible in /vendor/lib/hw/, /system/lib/, or via TEE introspection tools like 'tee-supplicant' or vendor-specific tee-daemon logs.Affected if The KeyMaster TA is loaded and active on the system.
-
Confirm key import functionality is exposedReview KeyMaster configuration and APIs to determine if key import operations are exposed to the HLOS. Check KeyMaster logs or debug output for keyimport method availability.Affected if Key import operations (KeyImport, ImportKey, or similar) are exposed and accessible from the Android/Linux userspace.
-
Check firmware version and patch levelRetrieve the firmware version and current security patch level from the device (e.g., 'getprop ro.build.version.security_patch', 'getprop vendor.qcom.version', or via '/proc/version'). Compare against known patched versions if available from the OEM.Affected if The installed firmware version corresponds to an unpatched build and the security patch level is older than the vendor release addressing CVE-2023-24850.
The device is likely affected if it uses one of the listed Qualcomm chips with an unpatched firmware version where the KeyMaster Trusted Application is enabled and accessible for key import operations.
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 the latest security patch updates provided by the device OEM that address this vulnerability in the KeyMaster component; monitor vendor security advisories for patch availability.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-24850 — 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-2023-24850 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