NVD / CVE Program· CNA qualcomm

CVE-2019-10531: Incorrect reading of system image resulting in buffer overflow when size of system image is increased in Snapdragon Auto, Snapdragon Mobile,

Noroxi assessment

Priority: Monitor (action score 39/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.90% (FIRST EPSS); higher than 59.8% of all records.
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.
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

Incorrect reading of system image resulting in buffer overflow when size of system image is increased in Snapdragon Auto, Snapdragon Mobile, Snapdragon Wearables in MDM9607, MSM8909W, Qualcomm 215, SD 210/SD 212/SD 205, SD 425, SD 439 / SD 429, SD 450, SD 625, SD 632, SDM439

CriticalCVSS 9.8 · v3.1—No exploit No fix recorded

Published: Nov 6, 2019
Updated: Jun 16, 2026
EPSS: 0.9% · 59th percentile
CWE: CWE-120

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 39 / 40 · 9.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.9%

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	mdm9607 firmware	cpe:2.3:o:qualcomm:mdm9607_firmware
qualcomm	mdm9607	cpe:2.3:h:qualcomm:mdm9607
qualcomm	msm8909w firmware	cpe:2.3:o:qualcomm:msm8909w_firmware
qualcomm	msm8909w	cpe:2.3:h:qualcomm:msm8909w
qualcomm	qualcomm 215 firmware	cpe:2.3:o:qualcomm:qualcomm_215_firmware
qualcomm	qualcomm 215	cpe:2.3:h:qualcomm:qualcomm_215
qualcomm	sd 210 firmware	cpe:2.3:o:qualcomm:sd_210_firmware
qualcomm	sd 210	cpe:2.3:h:qualcomm:sd_210
qualcomm	sd 212 firmware	cpe:2.3:o:qualcomm:sd_212_firmware
qualcomm	sd 212	cpe:2.3:h:qualcomm:sd_212
qualcomm	sd 205 firmware	cpe:2.3:o:qualcomm:sd_205_firmware
qualcomm	sd 205	cpe:2.3:h:qualcomm:sd_205

and 14 more

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

qualcomm mdm9607 firmwareall versions
qualcomm msm8909w firmwareall versions
qualcomm qualcomm 215 firmwareall versions
qualcomm sd 205 firmwareall versions
qualcomm sd 210 firmwareall versions
qualcomm sd 212 firmwareall versions
qualcomm sd 425 firmwareall versions
qualcomm sd 429 firmwareall versions
qualcomm sd 439 firmwareall versions
qualcomm sd 450 firmwareall versions
qualcomm sd 625 firmwareall versions
qualcomm sd 632 firmwareall versions
qualcomm sdm439 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 Mobile, Snapdragon Wearables
- MDM9607, MSM8909W, Qualcomm 215, SD 210/SD 212/SD 205, SD 425, SD 439 / SD 429, SD 450, SD 625, SD 632, SDM439affected

Same product

qualcomm: all records

Other highest-scoring records for the same primary product.

CVE-2019-2276Possible out of bound read occurs while processing beaconing request due to lack of check on action frames received from user controlled spa
39Monitor
CVE-2018-5915Exception in Modem IP stack while processing IPv6 packet in snapdragon automobile, snapdragon mobile and snapdragon wear in versions MDM9607
39Monitor
CVE-2016-10481In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Mobile and Snapdragon Wear MDM9206, MDM9607, MDM9635M, M
39Monitor

Published before and after this one in the same product

← EarlierCVE-2019-2312Jul 25, 2019 · When handling the vendor command there exists a potential buffer overflow due to lack of input validation of data buffer received in Snapdra
31Monitor
← EarlierCVE-2019-10492Sep 30, 2019 · Boot image not getting verified by AVB in Snapdragon Auto, Snapdragon Mobile, Snapdragon Wearables in MDM9607, MSM8909W, Qualcomm 215, SD 21
31Monitor
Later →CVE-2019-10537Dec 18, 2019 · Improper validation of event buffer extracted from FW response can lead to integer overflow, which will allow to pass the length check and e
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).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

TR-19-258 · Nov 10, 2019(Qualcomm Snapdragon Zafiyetleri)

All national notices →

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: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

Attack vector: Network
Attack complexity: Low
Privileges required: None
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-120 · Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Root cause

When data is copied, the source length is not compared with the size of the destination buffer. Excess data overwrites adjacent memory.

The bug in code

The whole CWE-120 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1char buf[256];
2memcpy(buf, pkt->data, pkt->len);

Fixed

1char buf[256];
2if (pkt->len > sizeof(buf)) {
3  return -EINVAL;
4}
5memcpy(buf, pkt->data, pkt->len);

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

—

Change log

No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

References

source.android.com/security/bulletin/

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records