dbcve.org
Apq8009 FirmwareOperating system · Qualcomm

CVE-2019-2295

MEDIUM · 5.5 CVSS v3.1 Published 2019-11-21
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
Information disclosure due to lack of address range check done on the SysDBG buffers in SDI code. in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wired Infrastructure and Networking in APQ8009, APQ8017, APQ8053, MDM9205, MSM8905, MSM8909, MSM8917, MSM8920, MSM8937, MSM8940, MSM8953, MSM8998, Nicobar, QCS404, QCS405, QCS605, QM215, SDA660, SDA845, SDM429, SDM439, SDM450, SDM630, SDM632, SDM636, SDM660, SDM670, SDM710, SDM845, SDM850, 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

Information disclosure vulnerability in Qualcomm Snapdragon chipsets caused by missing address range validation on SysDBG buffers within the Serial Debug Interface (SDI) code. The lack of bounds checking allows an attacker to read memory contents beyond the intended buffer boundaries, potentially exposing sensitive system data.

MitigationApply Qualcomm-provided firmware updates that include proper address range validation for SysDBG buffers in the SDI component. Users should obtain patched firmware from device manufacturers.

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
Apq8009 FirmwareOperating system
Affected:all versions
Apq8017 FirmwareOperating system
Affected:all versions
Apq8053 FirmwareOperating system
Affected:all versions
Mdm9205 FirmwareOperating system
Affected:all versions
Msm8905 FirmwareOperating system
Affected:all versions
Msm8909 FirmwareOperating system
Affected:all versions
Msm8917 FirmwareOperating system
Affected:all versions
Msm8920 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.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 checks

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

  1. Identify the Qualcomm chipset model
    On Linux-based embedded devices, check /proc/cpuinfo or use 'lsmem' and 'cat /proc/device-tree/model'. On Android, check Settings > About Phone or use 'getprop ro.hardware'
    Affected if The chipset model matches Apq8009, Apq8017, Apq8053, Mdm9205, Msm8905, Msm8909, Msm8917, or Msm8920
  2. Determine if Serial Debug Interface (SDI) is enabled
    Check debug configuration files or system properties related to SDI/SysDBG. Look for flags like 'sysdbg.enabled', 'debug.sdi.enable', or examine kernel command line parameters for early boot debugging settings
    Affected if SDI/SysDBG debug interface is actively enabled on the device
  3. Check firmware version information
    Query the baseband or modem firmware version via AT commands (if available) or check /firmware/image or /vendor/firmware partitions. On Android, use 'getprop' for ro.build.version.incremental or ro.mtk.version.baseband
    Affected if The device runs any firmware version on an affected chipset (all versions listed are vulnerable)
  4. Inspect memory access controls for debug buffers
    If you have kernel source access, review the SysDBG buffer allocation code in the SDI driver for bounds checking. Check if DMA buffers for debugging have proper address range validation implemented
    Affected if No address range validation exists on SysDBG buffer allocations in the SDI driver code

A device is affected if it uses any of the listed Qualcomm chipsets (Apq8009, Apq8017, Apq8053, Mdm9205, Msm8905, Msm8909, Msm8917, Msm8920) and has the SDI/SysDBG debug interface enabled, since all firmware versions for these chipsets lack proper bounds checking on debug buffers.

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 Qualcomm-provided firmware updates that include proper address range validation for SysDBG buffers in the SDI component. Users should obtain patched firmware from device manufacturers.

Fix this in Apq8009 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-2295 — 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-2295 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