NVD / CVE Program· CNA qualcomm

CVE-2019-10512: Payload size is not checked before using it as array index in audio in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdra

Noroxi assessment

Priority: Monitor (action score 31/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.19% (FIRST EPSS).
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.
According to the record, no fixed version is available yet.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Update when a fix is released; follow the vendor's advisory.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Payload size is not checked before using it as array index in audio in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking in IPQ4019, IPQ8064, IPQ8074, MDM9150, MDM9206, MDM9607, MDM9640, MDM9650, MSM8909W, MSM8996AU, 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 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, SDX24, SXR1130

HighCVSS 7.8 · v3.1—No exploit No fix recorded

Published: Nov 6, 2019
Updated: Jun 16, 2026
EPSS: 0.1% · 8th percentile
CWE: CWE-129

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 31 / 40 · 7.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.1%

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

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	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

and 84 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 mdm9150 firmwareall versions
qualcomm mdm9206 firmwareall versions
qualcomm mdm9607 firmwareall versions
qualcomm mdm9640 firmwareall versions
qualcomm mdm9650 firmwareall versions
qualcomm msm8909w firmwareall versions
qualcomm msm8996au 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

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, Snapdragon Wired Infrastruct
- IPQ4019, IPQ8064, IPQ8074, MDM9150, MDM9206, MDM9607, MDM9640, MDM9650, MSM8909W, MSM8996AU, QCS405, QCS605, Qualcomm 215, SD 210/SD 212/SD 205, SD 425, SD 427, SD 430, SD 435, SD 439 / SD 429, SD 450affected

Same product

qualcomm: all records

Other 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 resul
45Plan
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 Snapdra
39Monitor
CVE-2015-9199In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Automobile and Snapdragon Mobile IPQ4019, MDM9625, MDM96
39Monitor

Published before and after this one in the same product

← EarlierCVE-2019-10499Sep 30, 2019 · Improper validation of read and write index of tx and rx fifo`s before using for data copy from fifo can lead to out-of-bound access.
31Monitor
← EarlierCVE-2019-10491Nov 6, 2019 · ADSP can be compromised since it`s a general-purpose CPU processing untrusted data in Snapdragon Auto, Snapdragon Compute, Snapdragon Consum
31Monitor
Later →CVE-2019-2304Dec 18, 2019 · Integer overflow to buffer overflow due to lack of validation of event arguments received from firmware.
31Monitor

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.

No history yet (it accumulates with the daily EPSS job).

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 researchers

Finders, 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).