CVE-2021-1953: Improper handling of received malformed FTMR request frame can lead to reachable assertion while responding with FTM1 frame in Snapdragon…
Noroxi assessment
Priority: Monitor (action score 30/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.58% (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
Improper handling of received malformed FTMR request frame can lead to reachable assertion while responding with FTM1 frame 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
- Jul 13, 2021
- Updated
- Jun 16, 2026
- EPSS
- 0.5% · 48th percentile
- CWE
- CWE-617
Report tools
Action score
30
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.5%
CNA vs NVD score
- NVD
- 7.5
- CNA · qualcomm
- 7.5
- agree
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.
Is your version affected? Check itNoroxi 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 | 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 |
| qualcomm | ar9380 firmware | cpe:2.3:o:qualcomm:ar9380_firmware |
| qualcomm | ar9380 | cpe:2.3:h:qualcomm:ar9380 |
| qualcomm | csr8811 firmware | cpe:2.3:o:qualcomm:csr8811_firmware |
| qualcomm | csr8811 | cpe:2.3:h:qualcomm:csr8811 |
| qualcomm | csra6620 firmware | cpe:2.3:o:qualcomm:csra6620_firmware |
| qualcomm | csra6620 | cpe:2.3:h:qualcomm:csra6620 |
and 188 more
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
- AQT1000, AR8031, AR8035, AR9380, CSR8811, CSRA6620, CSRA6640, CSRB31024, IPQ4018, IPQ4028, IPQ4029, IPQ5010, IPQ5018, IPQ5028, IPQ6000, IPQ6005, IPQ6010, IPQ6018, IPQ6028, IPQ8064, IPQ8069, IPQ8070, Iaffected
Affected versions · NVD (20)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- 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 ipq4018 firmwareall versions
- qualcomm ipq4028 firmwareall versions
- qualcomm ipq4029 firmwareall versions
- qualcomm ipq5010 firmwareall versions
- qualcomm ipq5018 firmwareall versions
- qualcomm ipq5028 firmwareall versions
- qualcomm ipq6000 firmwareall versions
- qualcomm ipq6005 firmwareall versions
- qualcomm ipq6010 firmwareall versions
- qualcomm ipq6018 firmwareall versions
- qualcomm ipq6028 firmwareall versions
- qualcomm ipq8064 firmwareall versions
Same product
qualcomm: all recordsOther highest-scoring records for the same primary product.
- CVE-2025-21479Incorrect Authorization in GraphicsKEV64This week
- CVE-2025-21480Incorrect Authorization in Graphics WindowsKEV64This week
- CVE-2021-1965Possible buffer overflow due to lack of parameter length check during MBSSID scan IE parse in Snapdragon Auto, Snapdragon Compute…40Plan
Published before and after this one in the same product
- ← EarlierCVE-2021-1938Jul 13, 2021 · Possible assertion due to improper verification while creating and deleting the peer in Snapdragon Auto, Snapdragon Compute, Snapdragon…30Monitor
- ← EarlierCVE-2021-1940Jul 13, 2021 · Use after free can occur due to improper handling of response from firmware in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer…31Monitor
- Later →CVE-2021-1923Sep 8, 2021 · Incorrect pointer argument passed to trusted application TA could result in un-intended memory operations in Snapdragon Auto, Snapdragon…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.
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
- 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-617 · Reachable AssertionCVSS 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 (0)
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.