CVE-2021-1946
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 · uneditedNull Pointer Dereference may occur due to improper validation while processing crafted SDP body in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile
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 confidenceA null pointer dereference vulnerability exists in multiple Snapdragon product lines due to improper validation when parsing a specially crafted SDP (Session Description Protocol) body. The lack of sufficient input validation allows an attacker to trigger the null pointer dereference, potentially leading to denial of service or potentially remote code execution.
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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 modelOn Android devices, run 'getprop ro.hardware' or check /proc/cpuinfo for the processor identifier. On embedded devices, check the BOM (Bill of Materials) or device specifications for the Snapdragon model number.Affected if The chipset matches one of: Apq8017, Apq8053, Aqt1000, Ar8035, Msm8917, Msm8920, Msm8940, or Msm8953
-
Determine if SDP parsing is in useSearch application code or system services for SDP (Session Description Protocol) handling functions, such as those parsing SDP bodies in VoIP, WebRTC, or media streaming components. Inspect logs or network traffic for SDP message processing.Affected if The device or application actively parses SDP content, particularly in media signaling pathways
-
Check firmware version for patchesQuery the device firmware version through system settings, 'getprop ro.build.version.full', or the baseband/modem version string (AT+CGMR or through diag ports). Compare against any Qualcomm OEM security advisories.Affected if The firmware is the original unmodified version with no security patches applied, since all versions listed are affected
-
Assess network exposure to untrusted SDPReview firewall rules, network ACLs, and application source validation to determine if SDP content from untrusted or external network sources can reach the vulnerable parsing component.Affected if The device accepts or processes SDP from untrusted network sources without strict validation
You are affected if your device uses one of the listed Snapdragon chipsets and processes SDP content from any source, since all firmware versions for these models are vulnerable.
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/security updates from Qualcomm and affected device OEMs. Until patches are available, restrict processing of SDP content from untrusted sources and monitor for vendor advisories.
- 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-2021-1946 — 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-1946 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