CVE-2019-2275
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 · uneditedWhile deserializing any key blob during key operations, buffer overflow could occur exposing partial key information if any key operations are invoked(Depends on CVE-2018-13907) in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking in MDM9150, MDM9205, MDM9206, MDM9607, MDM9650, MSM8909W, MSM8996AU, QCS404, QCS605, Qualcomm 215, SD 210/SD 212/SD 205, SD 410/12, SD 425, SD 427, SD 430, SD 435, SD 439 / SD 429, SD 450, SD 625, SD 632, SD 636, SD 650/52, SD 712 / SD 710 / SD 670, SD 820, SD 820A, SD 835, SD 845 / SD 850, SD 855, SD 8CX, SDA660, SDM439, SDM630, SDM660, Snapdragon_High_Med_2016, SXR1130
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 · high confidenceBuffer overflow vulnerability in the key blob deserialization logic within Qualcomm Snapdragon chipset firmware. During key operations, improper bounds checking allows a buffer overflow that can expose partial cryptographic key information to an attacker. This vulnerability depends on CVE-2018-13907, suggesting a related cryptographic handling flaw in the same component.
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 Snapdragon chipset modelCheck the device or system documentation, kernel logs (dmesg | grep -i qualcomm), or hardware specifications to determine the exact Snapdragon chipset model number (e.g., Mdm9150, Mdm9205, Msm8909w, etc.)Affected if The chipset model matches any of these: Mdm9150, Mdm9205, Mdm9206, Mdm9607, Mdm9650, Msm8909w, Msm8996au, or Qcs404
-
Check the installed firmware versionRetrieve the firmware version through the device's system information, boot logs, or by querying the baseband processor version (e.g., at+cgmr, or through /proc/version, /proc/cpuinfo, or vendor-specific diagnostic tools)Affected if The firmware version is any version on an affected chipset (note: all versions of the listed chipsets are vulnerable)
-
Determine if key blob deserialization is in useMonitor or inspect cryptographic operations that involve key blob handling, such as key import, key wrap/unwrap, or secure key storage operations. Check application logs or system audit logs for key management API calls involving deserialization.Affected if The system performs cryptographic key operations that involve deserializing key blobs, as this is the specific component where the buffer overflow occurs
-
Verify if CVE-2018-13907 is also presentCVE-2018-13907 is a related cryptographic handling flaw in the same component. Check if your environment has indicators of the related vulnerability or if the firmware has not been patched for either CVE.Affected if The firmware has not been updated to address CVE-2018-13907, which indicates the component is likely unpatched for CVE-2019-2275 as well
You are affected if your device or system uses any of the listed Qualcomm Snapdragon chipset models (Mdm9150, Mdm9205, Mdm9206, Mdm9607, Mdm9650, Msm8909w, Msm8996au, or Qcs404) and performs cryptographic key operations involving key blob deserialization, as all firmware versions of these chipsets contain the vulnerability.
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 from OEM/device manufacturers. Users should check with their device vendors for available security patches addressing this vulnerability in affected Snapdragon chipsets.
- Consultation8.0 h
- Implementation40.0 h
- Testing24.0 h
- Review / QA16.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $24,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-2275 — 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-2019-2275 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