dbcve.org
Msm8909w FirmwareOperating system · Qualcomm

CVE-2019-2343

MEDIUM · 5.5 CVSS v3.0 Published 2019-07-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

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 · unedited
Out of bound read and information disclosure in firmware due to insufficient checking of an embedded structure that can be sent from a kernel driver in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables in MSM8909W, MSM8996AU, QCS605, Qualcomm 215, SD 210/SD 212/SD 205, SD 425, SD 427, SD 430, SD 435, SD 439 / SD 429, SD 450, SD 625, SD 632, SD 636, SD 665, SD 675, SD 712 / SD 710 / SD 670, SD 730, 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 confidence

Out-of-bounds read vulnerability in Qualcomm Snapdragon firmware allowing information disclosure due to insufficient validation of an embedded structure sent from a kernel driver. The flaw enables reading memory outside intended bounds, potentially exposing sensitive data.

MitigationApply vendor firmware/security updates from device manufacturers; this is a low-level firmware issue requiring patches from Qualcomm and downstream OEMs.

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 data
Msm8909w FirmwareOperating system
Affected:all versions
Msm8996au FirmwareOperating system
Affected:all versions
Qcs605 FirmwareOperating system
Affected:all versions
Qualcomm 215 FirmwareOperating system
Affected:all versions
Sd 210 FirmwareOperating system
Affected:all versions
Sd 212 FirmwareOperating system
Affected:all versions
Sd 205 FirmwareOperating system
Affected:all versions
Sd 425 FirmwareOperating system
Affected:all versions

CVSS 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.0/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the Qualcomm chipset model
    Check /proc/cpuinfo or dmesg for the chipset identifier (e.g., msm8909w, msm8996au, qcs605, sd210, sd212, sd205, sd425, or qualcomm 215)
    Affected if The chipset model matches one of the affected models listed in this CVE (Msm8909w, Msm8996au, Qcs605, Qualcomm 215, Sd 210, Sd 212, Sd 205, Sd 425)
  2. Confirm firmware version
    Query the baseband or radio firmware version via AT command (AT+CGMR) or through /system/build.prop entries (ro.build.version.all), or check manufacturer documentation for firmware version reporting
    Affected if Firmware version is present on any affected chipset model (all versions of listed chipsets are vulnerable)
  3. Verify vulnerable kernel driver presence
    Check loaded kernel modules via lsmod or /proc/modules for the specific kernel driver handling embedded structure validation from the kernel driver interface
    Affected if The kernel driver that processes the insufficiently validated embedded structure is loaded and active on the device
  4. Check for information disclosure indicators
    Review system logs (dmesg, logcat) for any out-of-bounds memory access errors, kernel panic messages related to memory read violations, or unexpected memory content in debug outputs
    Affected if Logs show out-of-bounds read errors or memory access violations originating from the affected kernel driver path

A device is affected if it uses any of the listed Qualcomm Snapdragon chipset models (Msm8909w, Msm8996au, Qcs605, Qualcomm 215, Sd 210, Sd 212, Sd 205, Sd 425) and runs the vulnerable firmware with the affected kernel driver module loaded.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor firmware/security updates from device manufacturers; this is a low-level firmware issue requiring patches from Qualcomm and downstream OEMs.

Fix this in Msm8909w Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-2343 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-2343 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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