Improper check before assigning value can lead to integer overflow in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdrag
Improper check before assigning value can lead to integer overflow 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 Wired Infrastructure and Networking in IPQ4019, IPQ8064, IPQ8074, MDM9206, MDM9607, MDM9640, MDM9650, MSM8996AU, QCA4020, QCA6174A, QCA6564, QCA6574, QCA6574AU, QCA6584, QCA6584AU, QCA8081, QCA9377, QCA9379, QCA9531, QCA9558, QCA9563, QCA9880, QCA9886, QCA9980, QCN5502, QCS605, SD 210/SD 212/SD 205, SD 425, SD 427, SD 430, SD 435, SD 450, SD 600, SD 625, SD 636, SD 675, SD 712 / SD 710 / SD 670, SD 820, SD 820A, SD 835, SD 845 / SD 850, SD 855, SD 8CX, SDA660, SDM630, SDM660, SDX20, SDX24, SM7150, Snapdragon_High_Med_2016, SXR1130
- Published
- May 24, 2019
- Updated
- Jun 16, 2026
- EPSS
- 0.2% · 10th percentile
- CWE
- CWE-190
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| qualcomm | ipq4019 firmware | cpe:2.3:o:qualcomm:ipq4019_firmware |
| qualcomm | ipq4019 | cpe:2.3:h:qualcomm:ipq4019 |
| qualcomm | ipq8064 firmware | cpe:2.3:o:qualcomm:ipq8064_firmware |
| qualcomm | ipq8064 | cpe:2.3:h:qualcomm:ipq8064 |
| qualcomm | ipq8074 firmware | cpe:2.3:o:qualcomm:ipq8074_firmware |
| qualcomm | ipq8074 | cpe:2.3:h:qualcomm:ipq8074 |
| qualcomm | mdm9206 firmware | cpe:2.3:o:qualcomm:mdm9206_firmware |
| qualcomm | mdm9206 | cpe:2.3:h:qualcomm:mdm9206 |
| qualcomm | mdm9607 firmware | cpe:2.3:o:qualcomm:mdm9607_firmware |
| qualcomm | mdm9607 | cpe:2.3:h:qualcomm:mdm9607 |
| qualcomm | mdm9640 firmware | cpe:2.3:o:qualcomm:mdm9640_firmware |
| qualcomm | mdm9640 | cpe:2.3:h:qualcomm:mdm9640 |
and 100 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- qualcomm ipq4019 firmwareall versions
- qualcomm ipq8064 firmwareall versions
- qualcomm ipq8074 firmwareall versions
- qualcomm mdm9206 firmwareall versions
- qualcomm mdm9607 firmwareall versions
- qualcomm mdm9640 firmwareall versions
- qualcomm mdm9650 firmwareall versions
- qualcomm msm8996au firmwareall versions
- qualcomm qca4020 firmwareall versions
- qualcomm qca6174a firmwareall versions
- qualcomm qca6564 firmwareall versions
- qualcomm qca6574 firmwareall versions
- qualcomm qca6574au firmwareall versions
- qualcomm qca6584 firmwareall versions
- qualcomm qca6584au firmwareall versions
- qualcomm qca8081 firmwareall versions
- qualcomm qca9377 firmwareall versions
- qualcomm qca9379 firmwareall versions
- qualcomm qca9531 firmwareall versions
- qualcomm qca9558 firmwareall versions
Versions reported by the vendor
Affected version ranges reported by the assigning authority (qualcomm). Independent of NVD's CPE analysis and usually ahead of it.
Qualcomm, Inc. Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapd
- IPQ4019, IPQ8064, IPQ8074, MDM9206, MDM9607, MDM9640, MDM9650, MSM8996AU, QCA4020, QCA6174A, QCA6564, QCA6574, QCA6574AU, QCA6584, QCA6584AU, QCA8081, QCA9377, QCA9379, QCA9531, QCA9558, QCA9563, QCA9affected
Same product
qualcomm: all recordsOther highest-scoring records for the same primary product.
- CVE-2020-11117u'In the lbd service, an external user can issue a specially crafted debug command to overwrite arbitrary files with arbitrary content resul45Plan
- CVE-2020-11172u'fscanf reads a string from a file and stores its contents on a statically allocated stack memory which leads to stack overflow' in Snapdra39Monitor
- CVE-2015-9199In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Automobile and Snapdragon Mobile IPQ4019, MDM9625, MDM9639Monitor
- CVE-2015-9152In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Automobile and Snapdragon Mobile IPQ4019, SD 210/SD 212/39Monitor
- CVE-2019-14063Out of bound access due to Invalid inputs to dapm mux settings which results into kernel failure in Snapdragon Auto, Snapdragon Compute, Sna36Monitor
- CVE-2018-13906The HMAC authenticating the message from QSEE is vulnerable to timing side channel analysis leading to potentially forged application messag36Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-190 · Integer Overflow or WraparoundCVSS vector
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.