CVE-2019-2236
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 · uneditedNull pointer dereference during secure application termination using specific application ids. in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wired Infrastructure and Networking in IPQ8074, MDM9206, MDM9607, MDM9650, MDM9655, MSM8996AU, QCA8081, QCS605, Qualcomm 215, SD 410/12, SD 425, SD 427, SD 430, SD 435, SD 439 / SD 429, SD 450, SD 625, SD 632, SD 636, SD 650/52, SD 675, SD 712 / SD 710 / SD 670, SD 730, SD 820, SD 820A, SD 835, 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 · moderate confidenceA null pointer dereference vulnerability exists in the secure application termination logic of multiple Qualcomm Snapdragon chipset generations. When specific application IDs are used during secure app termination, the system attempts to dereference a null pointer, leading to a crash or potential denial of service. This affects the secure termination path in trusted execution environments or security-focused application contexts.
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 dataall versionsall versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Qualcomm chipset modelDetermine the specific Qualcomm chipset or SoC model in your device. This is typically found in device specifications, hardware documentation, or by running commands like 'cat /proc/cpuinfo' on Linux-based embedded devices, or checking baseband info with 'at+cgmm' or similar AT commands on modems.Affected if The chipset model matches any of: Ipq8074, Mdm9206, Mdm9607, Mdm9650, Mdm9655, Msm8996au, Qca8081, or Qcs605
-
Verify firmware versionAttempt to retrieve the firmware version of the affected Qualcomm component. On many embedded/modem devices, this can be done via AT commands such as 'at+cgmr' or by checking /dev/ and system logs for baseband firmware version strings. On IPQ devices, check the bootloader or wireless firmware version.Affected if The firmware version cannot be determined or is present on the affected chipset models listed above, as all versions are currently affected per the advisory.
-
Check for secure termination usageDetermine whether the device utilizes trusted execution environment (TEE) features or secure application termination. This may require reviewing application configurations, security module settings, or consulting device/vendor documentation about secure app management features.Affected if Secure application termination logic or TEE-based security applications are actively used on the affected chipset, creating the condition where the null pointer dereference can trigger.
-
Review OEM security advisoriesCheck your device manufacturer's security advisory pages or firmware release notes for mentions of CVE-2019-2236 or Qualcomm security bulletins from 2019. OEM vendors typically publish CVEs addressed in their firmware updates.Affected if Your device OEM has not released a firmware update addressing CVE-2019-2236 for your specific hardware model, indicating the vulnerability remains present.
You are affected if your device uses any of the listed Qualcomm chipset models (Ipq8074, Mdm9206, Mdm9607, Mdm9650, Mdm9655, Msm8996au, Qca8081, Qcs605) and the OEM has not provided a firmware patch addressing this null pointer dereference in secure app termination logic.
Generated from the published advisory. Verify against your own configuration.
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 dataThis is a hardware/firmware-level vulnerability requiring a patch from the device OEM. End users should apply firmware updates provided by their device manufacturer. For embedded/IoT deployments, this requires updating the baseband/modem firmware from Qualcomm's monthly security patches and working with your hardware vendor for integration.
- Consultation8.0 h
- Implementation40.0 h
- Testing24.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $22,144.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-2236 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-2236 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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