CVE-2021-30349
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 · uneditedImproper access control sequence for AC database after memory allocation can lead to possible memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Voice & Music, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking
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 is an improper access control vulnerability in Qualcomm Snapdragon chips where the access control sequence for the AC (Access Control) database is incorrect after memory allocation, potentially leading to memory corruption. The flaw affects multiple Snapdragon product lines including Auto, Compute, Connectivity, Consumer IOT, Industrial IOT, Voice & Music, Wearables, and Wired Infrastructure components.
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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:H/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 model on the deviceCheck the device hardware specifications, bootloader output, or system information to determine the exact Snapdragon or Qualcomm chip variant (e.g., Aqt1000, Ar8031, Ar8035, Csr8811, Csra6620, Csra6640, Csrb31024, Fsm10055)Affected if The chip model matches any of the affected models listed in the CVE (Aqt1000, Ar8031, Ar8035, Csr8811, Csra6620, Csra6640, Csrb31024, or Fsm10055)
-
Retrieve the firmware version of the affected Qualcomm componentAccess the device firmware through manufacturer documentation, debug interfaces, or system firmware reading tools to obtain the exact firmware version string for the identified chipAffected if The firmware version is any version of the listed affected products (all versions are vulnerable)
-
Confirm the Access Control (AC) database feature is in useCheck the device configuration, firmware settings, or system logs to determine whether the Access Control database functionality is enabled or actively used on the chipAffected if The AC database feature is enabled or utilized on the vulnerable firmware
-
Check for vendor firmware update availabilityConsult the device manufacturer or Qualcomm product security advisories to verify if a patched firmware version has been released for the specific chip modelAffected if No vendor firmware update has been applied and the device runs the original affected firmware
A device is affected if it contains any of the listed Qualcomm chip models (Aqt1000, Ar8031, Ar8035, Csr8811, Csra6620, Csra6640, Csrb31024, Fsm10055) running their firmware with the AC database feature enabled and without vendor-supplied patches.
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 firmware updates provided by Qualcomm and propagated through device manufacturers. This is a chip-level vulnerability requiring vendor-supplied patches.
- Consultation8.0 h
- Implementation4.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 $9,856.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-30349 — 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-30349 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