dbcve.org
Mdm9205 FirmwareOperating system · Qualcomm

CVE-2019-2329

HIGH · 7.8 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 →
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
Use after free issue in cleanup routine due to missing pointer sanitization for a failed start of a trusted application. in Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wired Infrastructure and Networking in MDM9205, QCS404, QCS605, SDA845, SDM670, SDM710, SDM845, SDX55, SM6150, SM7150, SM8150, 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

Use after free vulnerability in the cleanup routine of trusted application initialization in Qualcomm Snapdragon processors. The vulnerability stems from missing pointer sanitization when a trusted application fails to start, leading to a dangling pointer that can be reused after being freed, allowing memory corruption and potential privilege escalation within the Trusted Execution Environment (TEE).

MitigationThis is a firmware-level vulnerability requiring a security patch from Qualcomm and subsequent OEM/firmware updates. No user mitigations available; affected device users should apply vendor patches when available.

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
Mdm9205 FirmwareOperating system
Affected:all versions
Qcs404 FirmwareOperating system
Affected:all versions
Qcs605 FirmwareOperating system
Affected:all versions
Sda845 FirmwareOperating system
Affected:all versions
Sdm670 FirmwareOperating system
Affected:all versions
Sdm710 FirmwareOperating system
Affected:all versions
Sdm845 FirmwareOperating system
Affected:all versions
Sdx55 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 or system information to determine the exact Qualcomm Snapdragon or other Qualcomm processor model (e.g., Mdm9205, Qcs404, Qcs605, Sda845, Sdm670, Sdm710, Sdm845, Sdx55)
    Affected if The device uses any of the following chipsets: Mdm9205, Qcs404, Qcs605, Sda845, Sdm670, Sdm710, Sdm845, or Sdx55. All firmware versions of these chipsets are affected.
  2. Verify TEE/TrustZone is enabled
    Check if the device implements Trusted Execution Environment (TEE), typically visible in boot logs, security settings, or by querying the TEE driver (e.g., /dev/tee0, /dev/teepriv0 on Linux-based devices)
    Affected if The TEE is present and active. The vulnerability exists in the trusted application initialization cleanup routine within the TEE.
  3. Confirm trusted application capability
    Determine if the device runs any trusted applications (TA) within the TEE. This may be visible in the secure element status, TEE manager logs, or by checking for TEE-aware applications in the system
    Affected if The device supports and runs trusted applications. The use-after-free occurs specifically during the initialization cleanup of trusted applications that fail to start.
  4. Check baseband or processor firmware version
    Query the device for the baseband processor firmware version or the secure processor (SP) firmware version using AT commands (*#9999#), service menus, or through diagnostic interfaces
    Affected if The firmware version corresponds to any of the affected chipset models listed. According to the provided data, all versions of the affected chipsets are vulnerable.

A user is affected if their device contains any of the listed Qualcomm chipsets (Mdm9205, Qcs404, Qcs605, Sda845, Sdm670, Sdm710, Sdm845, or Sdx55) and has TEE/TrustZone enabled with trusted application support, as all firmware versions of these chipsets contain the vulnerability.

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

This is a firmware-level vulnerability requiring a security patch from Qualcomm and subsequent OEM/firmware updates. No user mitigations available; affected device users should apply vendor patches when available.

Fix this in Mdm9205 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Testing12.0 h
  • Review / QA8.0 h
28.0 hours of engineering $4,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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