CVE Intelligence
Medium Cryptography

CVE-2020-3702 — Cleartext Transmission of Sensitive Information in Arista Access Point

u'Specifically timed and handcrafted traffic can cause internal errors in a WLAN device that lead to improper layer 2 Wi-Fi encryption with a consequent possibility of information disclosure over the air for a discrete set of traffic' in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking in APQ8053, IPQ4019, IPQ8064, MSM8909W, MSM8996AU, QCA9531, QCN5502, QCS405, SDX20, SM6150, SM7150

Published Sep 8, 2020 · Updated Oct 13, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: qualcomm

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.3% (30-day exploitation probability)+4
  • Technical severity (medium)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.33%
ahead of 24% of scored CVEs · Oct 14, 2026
Affects
Arista
Access Point and 13 more
CVSS base
6.5
Medium · 1 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
None
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Partial
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Arista Access Point, Debian Debian Linux, Qualcomm Apq8053 Firmware…).
  2. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  3. Search available logs for exploit probes matching the vulnerability class (cryptography), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Arista Access Point ≤ 8.8.3-12 Vulnerable NIST National Vulnerability Database
Debian Debian Linux version 10.0version 9.0 Vulnerable NIST National Vulnerability Database
Qualcomm Apq8053 Firmware versions not specified by the source Vulnerable NIST National Vulnerability Database
Qualcomm Ipq4019 Firmware versions not specified by the source Vulnerable NIST National Vulnerability Database
Qualcomm Ipq8064 Firmware versions not specified by the source Vulnerable NIST National Vulnerability Database
Qualcomm Msm8909w Firmware versions not specified by the source Vulnerable NIST National Vulnerability Database
Qualcomm Msm8996au Firmware versions not specified by the source Vulnerable NIST National Vulnerability Database
Qualcomm Qca9531 Firmware versions not specified by the source Vulnerable NIST National Vulnerability Database
Qualcomm Qcn5502 Firmware versions not specified by the source Vulnerable NIST National Vulnerability Database
Qualcomm Qcs405 Firmware versions not specified by the source Vulnerable NIST National Vulnerability Database
Qualcomm Sdx20 Firmware versions not specified by the source Vulnerable NIST National Vulnerability Database
Qualcomm Sm6150 Firmware versions not specified by the source Vulnerable NIST National Vulnerability Database
Qualcomm Sm7150 Firmware versions not specified by the source Vulnerable NIST National Vulnerability Database
Qualcomm Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, S version APQ8053, IPQ4019, IPQ8064, MSM8909W, MSM8996AU, QCA9531, QCN5502, QCS405, SDX20, Vulnerable CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Adjacent
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
6.5 CVSS 3.1 Medium 2.8 3.6 nvd@nist.gov via NIST National Vulnerability Database
3.3 CVSS 2.0 Low 6.5 2.9 nvd@nist.gov via NIST National Vulnerability Database
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N (score shown at the top: nvd@nist.gov)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-319 · Cleartext Transmission of Sensitive Information

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.33%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Check TLS negotiations and unexpected certificates in the component’s traffic.
network IDS/IPS

Timeline

What happened to this CVE, newest first.

  • 2026
  • Affected products added · qualcomm, inc./snapdragon auto, snapdragon compute, snapdragon connectivity, snapdragon consumer iot, snapdragon industr
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 13, 2026
  • CVSS changed · 6.5
    Oct 13, 2026 · NIST National Vulnerability Database
  • Source status changed · → Modified
    Oct 13, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 13, 2026 · NIST National Vulnerability Database
  • 2020
  • CVE published
    Sep 8, 2020 · qualcomm

Source activity

Repeated readings are counted rather than listed.

  • 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

5 on the record

Elsewhere on this site

Arista
every CVE for this vendor
Cryptography
same class
CWE-319
other pages naming this weakness

Related CVEs (same products)

  • High CVE-2026-12996 A use-after-free in OpenVPN 2.6.0 through 2.6.20 and 2.7_alpha1 through 2.7.4 allows remote... Jul 30, 2026
  • Medium CVE-2026-14355 ext/openssl: Memory corruption in openssl_encrypt with AES-WRAP-PAD Jul 3, 2026
  • Medium CVE-2026-56968 Use of Uninitialized Resource in Gnu Sasl Jun 23, 2026
  • High CVE-2026-49975 Apache HTTP Server: mod_http2 denial of service Jun 8, 2026
  • High CVE-2026-24088 Missing Authentication for Critical Function in Boot Jun 1, 2026
  • High CVE-2026-9256 NGINX ngx_http_rewrite_module vulnerability May 22, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No fixed version, patch or mitigation documented.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2020-3702 is "Cleartext Transmission of Sensitive Information in Arista Access Point", rated Medium. It affects Access Point (Arista); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 6.5 describes technical severity. EPSS 0.33% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.