dbcve.org
Apq8009 FirmwareOperating system · Qualcomm

CVE-2019-2288

HIGH · 7.8 CVSS v3.1 Published 2019-12-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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 write in TZ while copying the secure dump structure on HLOS provided buffer as a part of memory dump 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, APQ8096, APQ8096AU, APQ8098, IPQ8074, MDM9150, MDM9206, MDM9607, MDM9650, MSM8905, MSM8909, MSM8917, MSM8920, MSM8937, MSM8940, MSM8953, MSM8976, MSM8996, MSM8996AU, MSM8998, QCA8081, 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

Out-of-bounds write vulnerability in Qualcomm's TrustZone (TZ) secure operating system during memory dump operations. The flaw exists when copying a secure dump structure into a buffer provided by the HLOS (High-Level Operating System), where insufficient bounds checking allows data to be written beyond the allocated buffer boundaries, potentially enabling privilege escalation or arbitrary code execution within the trusted execution environment.

MitigationApply vendor-supplied firmware/security patches from device OEMs that address the TZ memory dump vulnerability. Since this is a firmware-level issue in the TrustZone component, remediation requires updating the device's baseband or system-on-chip (SoC) firmware from the original equipment manufacturer.

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
Apq8096 FirmwareOperating system
Affected:all versions
Apq8096au FirmwareOperating system
Affected:all versions
Apq8098 FirmwareOperating system
Affected:all versions
Ipq8074 FirmwareOperating system
Affected:all versions
Mdm9150 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
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/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 checks

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

  1. Identify the Qualcomm SoC model
    Check /proc/cpuinfo, /sys/devices/soc0/soc_id, /sys/firmware/devicetree/base/compatible, or use 'getprop ro.hardware' on Android devices
    Affected if The SoC model matches one of the affected chipsets: Apq8009, Apq8017, Apq8053, Apq8096, Apq8096au, Apq8098, Ipq8074, or Mdm9150
  2. Verify the SoC is from the affected product line
    Confirm the chipset is a Qualcomm processor from the listed product families. Cross-reference the SoC identifier found in step 1 against the CVE-affected model list
    Affected if The device uses any of the eight listed Qualcomm firmware products regardless of version number
  3. Confirm TrustZone memory dump capability exists
    This is an intrinsic feature of the TrustZone implementation on affected SoCs. No user-accessible config to check - the vulnerability exists in the TZ secure OS memory dump code path
    Affected if The device has TrustZone enabled (standard on all affected Qualcomm SoCs) and supports memory dump operations - which is the default state on these platforms
  4. Check baseband firmware version for inventory
    On Android, check 'getprop gsm.version.baseband' or /proc/version. On embedded Linux, check /proc/firmware or bootloader info if accessible
    Affected if Not directly indicative of vulnerability status - all versions of affected SoCs are vulnerable. This step is for inventory/classification purposes only

The device is affected if it uses any of the listed Qualcomm SoC models (Apq8009, Apq8017, Apq8053, Apq8096, Apq8096au, Apq8098, Ipq8074, Mdm9150) regardless of firmware version, as the vulnerability exists in the TrustZone memory dump code path on these chipsets.

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-supplied firmware/security patches from device OEMs that address the TZ memory dump vulnerability. Since this is a firmware-level issue in the TrustZone component, remediation requires updating the device's baseband or system-on-chip (SoC) firmware from the original equipment manufacturer.

Fix this in Apq8009 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Testing16.0 h
  • Review / QA8.0 h
32.0 hours of engineering $5,440
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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