Null pointer dereference can occur while parsing invalid chunks while playing the nonstandard clip in Snapdragon Auto, Snapdragon Compute, S
Null pointer dereference can occur while parsing invalid chunks while playing the nonstandard clip in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables in MDM9150, MDM9206, MDM9607, MDM9650, MSM8909W, MSM8996AU, QCA6574AU, QCS405, QCS605, Qualcomm 215, SD 210/SD 212/SD 205, SD 425, SD 427, SD 430, SD 435, SD 439 / SD 429, SD 450, SD 600, SD 615/16/SD 415, SD 625, SD 632, SD 636, SD 665, SD 675, SD 712 / SD 710 / SD 670, SD 730, SD 820, SD 820A, SD 835, SD 845 / SD 850, SD 855, SDA660, SDM439, SDM630, SDM660, SDX20
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; 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 help- Published
- Nov 6, 2019
- Updated
- Jun 16, 2026
- EPSS
- 0.8% · 55th percentile
- CWE
- CWE-476
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
30
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.8%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| qualcomm | mdm9150 firmware | cpe:2.3:o:qualcomm:mdm9150_firmware |
| qualcomm | mdm9150 | cpe:2.3:h:qualcomm:mdm9150 |
| 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 | mdm9650 firmware | cpe:2.3:o:qualcomm:mdm9650_firmware |
| qualcomm | mdm9650 | cpe:2.3:h:qualcomm:mdm9650 |
| qualcomm | msm8909w firmware | cpe:2.3:o:qualcomm:msm8909w_firmware |
| qualcomm | msm8909w | cpe:2.3:h:qualcomm:msm8909w |
| qualcomm | msm8996au firmware | cpe:2.3:o:qualcomm:msm8996au_firmware |
| qualcomm | msm8996au | cpe:2.3:h:qualcomm:msm8996au |
and 76 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- qualcomm mdm9150 firmwareall versions
- qualcomm mdm9206 firmwareall versions
- qualcomm mdm9607 firmwareall versions
- qualcomm mdm9650 firmwareall versions
- qualcomm msm8909w firmwareall versions
- qualcomm msm8996au firmwareall versions
- qualcomm qca6574au firmwareall versions
- qualcomm qcs405 firmwareall versions
- qualcomm qcs605 firmwareall versions
- qualcomm qualcomm 215 firmwareall versions
- qualcomm sd 205 firmwareall versions
- qualcomm sd 210 firmwareall versions
- qualcomm sd 212 firmwareall versions
- qualcomm sd 415 firmwareall versions
- qualcomm sd 425 firmwareall versions
- qualcomm sd 427 firmwareall versions
- qualcomm sd 429 firmwareall versions
- qualcomm sd 430 firmwareall versions
- qualcomm sd 435 firmwareall versions
- qualcomm sd 439 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 Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables
- MDM9150, MDM9206, MDM9607, MDM9650, MSM8909W, MSM8996AU, QCA6574AU, QCS405, QCS605, Qualcomm 215, SD 210/SD 212/SD 205, SD 425, SD 427, SD 430, SD 435, SD 439 / SD 429, SD 450, SD 600, SD 615/16/SD 41affected
Same product
qualcomm: all recordsOther highest-scoring records for the same primary product.
- CVE-2019-2332Memory corruption while accessing the memory as payload size is not validated before access in Snapdragon Auto, Snapdragon Compute, Snapdrag39Monitor
- CVE-2019-2331Possible Integer overflow because of subtracting two integers without checking if the result would overflow or not in Snapdragon Auto, Snapd39Monitor
- CVE-2019-2325Out of boundary access due to token received from ADSP and is used without validation as an index into the array in Snapdragon Auto, Snapdra39Monitor
- CVE-2019-2324When ADSP is compromised, the audio port index that`s returned from ADSP might be out of the valid range and leads to out of boundary access39Monitor
- CVE-2019-2323Lack of check to ensure crypto engine data passed by user is initialized can result in bus error in Snapdragon Auto, Snapdragon Compute, Sna39Monitor
- CVE-2019-2283Improper validation of read and write index of tx and rx fifo`s before calculating pointer can lead to out-of-bound access in Snapdragon Aut39Monitor
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
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-476 · NULL Pointer DereferenceCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change 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.