CVE-2021-1929
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 · uneditedLack of strict validation of bootmode can lead to information disclosure in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, 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 confidenceThis vulnerability involves insufficient validation of the boot mode in Qualcomm Snapdragon chipsets across multiple product lines (Auto, Compute, Connectivity, Consumer IOT, Industrial IOT, Mobile, Wearables). The lack of strict validation allows an attacker to potentially access sensitive information through improper boot mode handling.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Qualcomm chipset modelDetermine the specific Snapdragon chipset or firmware identifier used in the device. This can be found in system documentation, device specifications, bootloader information, or by querying the device's firmware/BOM (Bill of Materials) if you have access.Affected if The chipset model matches one of: Apq8096au, Aqt1000, Msm8996au, Qca6390, Qca6391, Qca6420, Qca6421, or Qca6426
-
Check the firmware versionQuery the device or firmware to obtain the installed firmware version. This may require access to the bootloader, device management interface, or firmware dump, depending on the product type (Auto, Compute, Mobile, IOT, Wearables, etc.).Affected if Any firmware version is installed on one of the affected chipset models, since the advisory lists all versions as affected
-
Verify boot mode security configurationInspect the bootloader's secure boot configuration and boot mode validation settings. This typically requires access to the firmware image, bootloader configuration files, or JTAG/debug interfaces to examine how boot mode is validated during the boot sequence.Affected if The boot mode validation is not strictly enforced, allowing improper boot mode handling that could expose sensitive information
-
Confirm product line falls within affected scopeIdentify the product category (Auto, Compute, Connectivity, Consumer IOT, Industrial IOT, Mobile, or Wearables) in which the device operates, as the vulnerability spans multiple Qualcomm product lines.Affected if The device is part of any of these Qualcomm product lines using the affected chipset models
You are affected if your device uses any of the listed Qualcomm chipset models (Apq8096au, Aqt1000, Msm8996au, Qca6390, Qca6391, Qca6420, Qca6421, Qca6426) regardless of firmware version, and improper boot mode validation is present in the bootloader.
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 devices. This requires coordination with Qualcomm and/or device OEMs to obtain and deploy patched bootloaders with proper bootmode validation.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.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 $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-1929 — 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-2021-1929 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