NVD / CVE Program· CNA qualcomm

CVE-2020-11172: u'fscanf reads a string from a file and stores its contents on a statically allocated stack memory which leads to stack overflow' in…

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

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.74% (FIRST EPSS); higher than 55.3% 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.

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

u'fscanf reads a string from a file and stores its contents on a statically allocated stack memory which leads to stack overflow' in Snapdragon Wired Infrastructure and Networking in IPQ4019, IPQ6018, IPQ8064, IPQ8074, QCA9531, QCA9980

Published: Nov 2, 2020
Updated: Jun 16, 2026
EPSS: 0.7% · 55th 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.7%

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.

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	ipq6018 firmware	cpe:2.3:o:qualcomm:ipq6018_firmware
qualcomm	ipq6018	cpe:2.3:h:qualcomm:ipq6018
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	qca9531 firmware	cpe:2.3:o:qualcomm:qca9531_firmware
qualcomm	qca9531	cpe:2.3:h:qualcomm:qca9531
qualcomm	qca9980 firmware	cpe:2.3:o:qualcomm:qca9980_firmware
qualcomm	qca9980	cpe:2.3:h:qualcomm:qca9980

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 Wired Infrastructure and Networking
- IPQ4019, IPQ6018, IPQ8064, IPQ8074, QCA9531, QCA9980affected

Affected versions · NVD (6)

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

qualcomm ipq4019 firmwareall versions
qualcomm ipq6018 firmwareall versions
qualcomm ipq8064 firmwareall versions
qualcomm ipq8074 firmwareall versions
qualcomm qca9531 firmwareall versions
qualcomm qca9980 firmwareall versions

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…
45Plan
CVE-2015-9199In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Automobile and Snapdragon Mobile IPQ4019, MDM9625…
39Monitor
CVE-2015-9152In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Automobile and Snapdragon Mobile IPQ4019, SD 210/SD…
39Monitor

Published before and after this one in the same product

← EarlierCVE-2019-10512Nov 6, 2019 · Payload size is not checked before using it as array index in audio in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT…
31Monitor
← EarlierCVE-2019-2304Dec 18, 2019 · Integer overflow to buffer overflow due to lack of validation of event arguments received from firmware.
31Monitor
← EarlierCVE-2019-14063Feb 7, 2020 · Out of bound access due to Invalid inputs to dapm mux settings which results into kernel failure in Snapdragon Auto, Snapdragon Compute…
36Monitor

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.

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

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 (0)

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

References

www.qualcomm.com/company/product-security/bulletins/october-2020-bulletin

Show all references (1 more)

www.qualcomm.com/company/product-security/bulletins/october-2020-security-bulletin

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

All records