CVE-2022-22069
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 · uneditedDevices with keyprotect off may store unencrypted keybox in RPMB and cause cryptographic issue in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables
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 confidenceWhen KeyProtect is disabled on affected Qualcomm Snapdragon chips, cryptographic keyboxes are stored in unencrypted form in the Replay Protected Memory Block (RPMB) partition. This allows potential extraction or manipulation of cryptographic keys, compromising the security of encryption operations.
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 Snapdragon chip modelCheck system information or hardware specifications to determine if the device uses one of the affected chips: Aqt1000, Qca6390, Qca6391, Qca6420, Qca6421, Qca6426, Qca6430, or Qca6431.Affected if The device contains any of the listed affected chip models.
-
Determine firmware versionQuery the firmware version of the Qualcomm chip using available system diagnostics, vendor tools, or by reading /sys/class/firmware or similar firmware reporting interfaces if accessible.Affected if The firmware version matches any of the listed affected products (all versions of Aqt1000, Qca6390, Qca6391, Qca6420, Qca6421, Qca6426, Qca6430, Qca6431).
-
Check KeyProtect statusUse vendor-specific diagnostic tools or hardware security interfaces to query the KeyProtect configuration status. This may require access to secure boot debug interfaces or Qualcomm-specific tooling.Affected if KeyProtect is reported as disabled or not properly initialized.
-
Inspect RPMB key storage configurationExamine the RPMB partition configuration and key storage settings through low-level storage inspection tools or vendor-provided security diagnostics to verify whether keyboxes are encrypted at rest.Affected if Keyboxes in RPMB are stored in unencrypted plaintext form rather than being protected by KeyProtect encryption.
A user is affected if their device contains any of the listed Qualcomm chips with firmware versions as specified AND KeyProtect is disabled, resulting in unencrypted key storage in RPMB.
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-supplied firmware updates for affected Snapdragon components to re-enable KeyProtect and ensure cryptographic keys are properly encrypted at rest in RPMB.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-22069 — 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-2022-22069 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