CVE-2021-1980: Possible buffer over read due to lack of length check while parsing beacon IE response in Snapdragon Auto, Snapdragon Compute, Snapdragon Co
Noroxi assessment
Priority: Monitor (action score 36/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.61% (FIRST EPSS).
- 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
Possible buffer over read due to lack of length check while parsing beacon IE response in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wired Infrastructure and Networking
- Published
- Oct 20, 2021
- Updated
- Jun 16, 2026
- EPSS
- 0.6% · 49th percentile
- CWE
- CWE-125
Report tools
Action score
36
Monitor
Low priority for now.
- CVSS
- 36 / 40 · 9.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.6%
CNA vs NVD score
- NVD
- 9.1
- CNA · qualcomm
- 7.5
- 1.6 point gap
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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
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 helpAffected 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 | apq8053 firmware | cpe:2.3:o:qualcomm:apq8053_firmware |
| qualcomm | apq8053 | cpe:2.3:h:qualcomm:apq8053 |
| qualcomm | apq8064au firmware | cpe:2.3:o:qualcomm:apq8064au_firmware |
| qualcomm | apq8064au | cpe:2.3:h:qualcomm:apq8064au |
| qualcomm | apq8096au firmware | cpe:2.3:o:qualcomm:apq8096au_firmware |
| qualcomm | apq8096au | cpe:2.3:h:qualcomm:apq8096au |
| qualcomm | aqt1000 firmware | cpe:2.3:o:qualcomm:aqt1000_firmware |
| qualcomm | aqt1000 | cpe:2.3:h:qualcomm:aqt1000 |
| qualcomm | ar8031 firmware | cpe:2.3:o:qualcomm:ar8031_firmware |
| qualcomm | ar8031 | cpe:2.3:h:qualcomm:ar8031 |
| qualcomm | ar8035 firmware | cpe:2.3:o:qualcomm:ar8035_firmware |
| qualcomm | ar8035 | cpe:2.3:h:qualcomm:ar8035 |
and 188 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- qualcomm apq8053 firmwareall versions
- qualcomm apq8064au firmwareall versions
- qualcomm apq8096au firmwareall versions
- qualcomm aqt1000 firmwareall versions
- qualcomm ar8031 firmwareall versions
- qualcomm ar8035 firmwareall versions
- qualcomm ar9380 firmwareall versions
- qualcomm csr8811 firmwareall versions
- qualcomm csra6620 firmwareall versions
- qualcomm csra6640 firmwareall versions
- qualcomm csrb31024 firmwareall versions
- qualcomm fsm10055 firmwareall versions
- qualcomm fsm10056 firmwareall versions
- qualcomm ipq4018 firmwareall versions
- qualcomm ipq4019 firmwareall versions
- qualcomm ipq4028 firmwareall versions
- qualcomm ipq4029 firmwareall versions
- qualcomm ipq5010 firmwareall versions
- qualcomm ipq5018 firmwareall versions
- qualcomm ipq5028 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 Mobile, Snapdragon Voice & Mu
- APQ8053, APQ8064AU, APQ8096AU, AQT1000, AR8031, AR8035, AR9380, CSR8811, CSRA6620, CSRA6640, CSRB31024, FSM10055, FSM10056, IPQ4018, IPQ4019, IPQ4028, IPQ4029, IPQ5010, IPQ5018, IPQ5028, IPQ6000, IPQ6affected
Same product
qualcomm: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-22071Possible use after free when process shell memory is freed using IOCTL munmap call and process initialization is in progress in Snapdragon AKEV61This week
- CVE-2020-11264Improper authentication of Non-EAPOL/WAPI plaintext frames during four-way handshake can lead to arbitrary network packet injection in Snapd43Plan
- CVE-2020-11153u'Out of bound memory access while processing GATT data received due to lack of check of pdu data length and leads to remote code execution'40Plan
Published before and after this one in the same product
- ← EarlierCVE-2021-1970Jul 13, 2021 · Possible out of bound read due to lack of length check of FT sub-elements in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, S30Monitor
- ← EarlierCVE-2021-1948Sep 9, 2021 · Possible out of bound read due to lack of length check of data while parsing the beacon or probe response in Snapdragon Auto, Snapdragon Com30Monitor
- Later →CVE-2021-30306Oct 20, 2021 · Possible buffer over read due to improper buffer allocation for file length passed from user space in Snapdragon Auto, Snapdragon Connectivi28Monitor
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
- high · data can be read
- 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
- High
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-125 · Out-of-bounds ReadCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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.
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
Vendor advisories and official records. Exploit/PoC links are deliberately left out.