CVE-2021-1896: Weak configuration in WLAN could cause forwarding of unencrypted packets from one client to another in Snapdragon Compute, Snapdragon Connec
Noroxi assessment
Priority: Monitor (action score 17/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.17% (FIRST EPSS).
- Someone on the same network segment 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
Weak configuration in WLAN could cause forwarding of unencrypted packets from one client to another in Snapdragon Compute, Snapdragon Connectivity
- Published
- Jul 13, 2021
- Updated
- Jun 16, 2026
- EPSS
- 0.1% · 6th percentile
- CWE
- CWE-319
Report tools
Action score
17
Monitor
Low priority for now.
- CVSS
- 17 / 40 · 4.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CNA vs NVD score
- NVD
- 4.3
- CNA · qualcomm
- 4.3
- 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.
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 | aqt1000 firmware | cpe:2.3:o:qualcomm:aqt1000_firmware |
| qualcomm | aqt1000 | cpe:2.3:h:qualcomm:aqt1000 |
| qualcomm | qca6164 firmware | cpe:2.3:o:qualcomm:qca6164_firmware |
| qualcomm | qca6164 | cpe:2.3:h:qualcomm:qca6164 |
| qualcomm | qca6174 firmware | cpe:2.3:o:qualcomm:qca6174_firmware |
| qualcomm | qca6174 | cpe:2.3:h:qualcomm:qca6174 |
| qualcomm | qca6174a firmware | cpe:2.3:o:qualcomm:qca6174a_firmware |
| qualcomm | qca6174a | cpe:2.3:h:qualcomm:qca6174a |
| qualcomm | qca6420 firmware | cpe:2.3:o:qualcomm:qca6420_firmware |
| qualcomm | qca6420 | cpe:2.3:h:qualcomm:qca6420 |
| qualcomm | qca6430 firmware | cpe:2.3:o:qualcomm:qca6430_firmware |
| qualcomm | qca6430 | cpe:2.3:h:qualcomm:qca6430 |
and 32 more
Check your site's encryption
This vulnerability is about certificate validation or weak cryptography. The free SSL checker tests your certificate, enabled TLS versions and weak ciphers.
Run the SSL checkAffected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- qualcomm aqt1000 firmwareall versions
- qualcomm qca6164 firmwareall versions
- qualcomm qca6174 firmwareall versions
- qualcomm qca6174a firmwareall versions
- qualcomm qca6420 firmwareall versions
- qualcomm qca6430 firmwareall versions
- qualcomm qca9377 firmwareall versions
- qualcomm sc8180x firmwareall versions
- qualcomm sd 8c firmwareall versions
- qualcomm sd 8cx firmwareall versions
- qualcomm sd7c firmwareall versions
- qualcomm sd850 firmwareall versions
- qualcomm sdx55 firmwareall versions
- qualcomm sm6250 firmwareall versions
- qualcomm wcd9340 firmwareall versions
- qualcomm wcd9341 firmwareall versions
- qualcomm wcn3990 firmwareall versions
- qualcomm wcn3991 firmwareall versions
- qualcomm wcn3998 firmwareall versions
- qualcomm wcn6850 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 Compute, Snapdragon Connectivity
- AQT1000, QCA6164, QCA6174, QCA6174A, QCA6420, QCA6430, QCA9377, SC8180X+SDX55, SD 8C, SD 8CX, SD7c, SD850, SM6250, WCD9340, WCD9341, WCN3990, WCN3991, WCN3998, WCN6850, WSA8810, WSA8815affected
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, Snapdrago40Plan
Published before and after this one in the same product
- ← EarlierCVE-2020-11306Jun 9, 2021 · Possible integer overflow in RPMB counter due to lack of length check on user provided data in Snapdragon Auto, Snapdragon Compute, Snapdrag31Monitor
- ← EarlierCVE-2021-1937Jun 9, 2021 · Reachable assertion is possible while processing peer association WLAN message from host and nonstandard incoming packet in Snapdragon Auto,30Monitor
- Later →CVE-2021-1931Jul 13, 2021 · Possible buffer overflow due to improper validation of buffer length while processing fast boot commands in Snapdragon Auto, Snapdragon Comp26Monitor
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 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
- Someone on the same network segment 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
- low · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Adjacent
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-319 · Cleartext Transmission of Sensitive InformationCVSS vector
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
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.