dbcve.org
Apq8009 FirmwareOperating system · Qualcomm

CVE-2019-2321

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
Incorrect length used while validating the qsee log buffer sent from HLOS which could then lead to remap conflict 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 APQ8009, APQ8017, APQ8053, APQ8096, APQ8096AU, APQ8098, IPQ4019, IPQ8074, MDM9150, MDM9205, MDM9206, MDM9207C, MDM9607, MDM9650, MSM8905, MSM8909, MSM8909W, MSM8917, MSM8920, MSM8937, MSM8939, MSM8940, MSM8953, MSM8996, MSM8996AU, MSM8998, QCA8081, QCS404, QCS605, QM215, SDA660, SDA845, SDM429, SDM439, SDM450, SDM630, SDM632, SDM636, SDM660, SDM670, SDM710, SDM845, SDM850, SDX24, SM6150, SM7150, SM8150, Snapdragon_High_Med_2016, SXR1130, SXR2130

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

A length validation vulnerability exists in the QSEE (Qualcomm Secure Execution Environment) log buffer handling. When HLOS (High Level Operating System) sends a log buffer to QSEE, an incorrect length value is used during validation, which can cause a memory remap conflict. This could potentially allow an attacker to corrupt memory or escalate privileges within the trusted execution environment.

MitigationApply vendor-provided firmware updates from Qualcomm or device manufacturers that include the security patch for CVE-2019-2321. This is a firmware-level fix that requires updating the baseband processor or system-on-chip firmware.

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
Ipq4019 FirmwareOperating system
Affected:all versions
Ipq8074 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 chipset model
    Check the device specifications, system-on-chip (SoC) information, or use commands like 'cat /proc/cpuinfo' on Android devices to determine the exact chipset (e.g., Apq8009, Apq8017, Apq8053, Apq8096, Ipq4019, Ipq8074)
    Affected if The chipset matches one of the following: Apq8009, Apq8017, Apq8053, Apq8096, Apq8096au, Apq8098, Ipq4019, or Ipq8074
  2. Verify the firmware version
    Retrieve the baseband processor firmware version through device diagnostics, modem logs, or Android's 'getprop' command (e.g., 'getprop ro.baseband', 'getprop gsm.version.baseband')
    Affected if The device uses one of the affected chipset models regardless of firmware version, as all versions are listed as affected
  3. Confirm QSEE/TEE is present
    Verify that the device uses Qualcomm's Secure Execution Environment (QSEE) or TrustZone by checking for related system properties, secure kernel features, or examining TEE log buffers if accessible
    Affected if The device implements QSEE/TrustZone and the chipset is one of the affected models
  4. Check for QSEE log buffer interaction
    Examine any available QSEE or secure kernel logs, or verify if HLOS-to-QSEE communication interfaces exist on the device (this typically requires privileged access)
    Affected if The device supports log buffer communication between HLOS and QSEE and uses an affected chipset

A device is affected if it contains any of the listed Qualcomm chipsets (Apq8009, Apq8017, Apq8053, Apq8096, Apq8096au, Apq8098, Ipq4019, Ipq8074) and utilizes QSEE for secure execution, as all firmware versions of these chipsets are vulnerable.

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-provided firmware updates from Qualcomm or device manufacturers that include the security patch for CVE-2019-2321. This is a firmware-level fix that requires updating the baseband processor or system-on-chip firmware.

Fix this in Apq8009 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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