CVE-2020-3702

MEDIUMNVD 6.56.5—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.5 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 73% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.5Exploit: None knownExposed: 0

A fix is available — apply it.

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

CVSS v3
6.5
EG Score
6.5(medium)
EG Risk
34(Track)
EG Risk 34/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity65% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
28%
KEV
Not listed

Published

September 8, 2020

Last Modified

November 21, 2024

References (10)

Patch Availability(6)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-headers-5.11.0-1021-raspi (5.11.0-1021.22) @ hirsute2026-05-26ubuntu
ubuntulinux-virtual-hwe-16.04-edge (4.15.0.161.154) @ xenial2026-05-26ubuntu
ubuntulinux-image-lowlatency (5.4.0.89.93) @ focal2026-05-26ubuntu
ubuntulinux-tools-oem-20.04-edge (5.10.0.1050.52) @ focal2026-05-26ubuntu
ubuntulinux-image-lowlatency (4.4.0.223.230) @ xenial2026-05-26ubuntu
ubuntulinux-gkeop-5.4-headers-5.4.0-1025 (5.4.0-1025.26~18.04.1) @ bionic2026-05-26ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(6 across 5 ecosystems)
Debian:9(2)
PackageVulnerable rangeFixed inDependents
linux4.9.107-1 ... 4.9.88-1~bpo8+1 (68 versions)4.9.290-1—
linux-4.194.19.132-1~deb9u1 ... 4.19.194-3~deb9u1 (9 versions)4.19.208-1~deb9u1—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.46-45.10.46-5—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux—5.14.6-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux—5.14.6-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux—5.14.6-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(6)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 6× in last 7d / 24× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 145 total refreshes for this CVE.

  1. 2026-09-19 15:37 UTCEPSS rescore
  2. 2026-09-18 19:23 UTCEPSS rescore
  3. 2026-09-17 19:22 UTCEPSS rescore
  4. 2026-09-16 14:04 UTCEPSS rescore
  5. 2026-09-15 03:06 UTCEPSS rescore
  6. 2026-09-13 16:43 UTCEPSS rescore
  7. 2026-09-12 14:57 UTCEPSS rescore
  8. 2026-09-11 09:32 UTCEPSS rescore
  9. 2026-09-08 21:56 UTCEPSS rescore
  10. 2026-09-07 15:57 UTCEPSS rescore
  11. 2026-09-07 02:18 UTCOSV refresh
  12. 2026-09-06 13:44 UTCEPSS rescore
  13. 2026-09-05 15:24 UTCEPSS rescore
  14. 2026-09-04 13:57 UTCEPSS rescore
  15. 2026-09-04 05:03 UTCEPSS rescore
  16. 2026-09-02 14:08 UTCEPSS rescore
  17. 2026-09-01 03:32 UTCEPSS rescore
  18. 2026-08-30 19:14 UTCEPSS rescore
  19. 2026-08-30 01:18 UTCEPSS rescore
  20. 2026-08-27 14:21 UTCEPSS rescore
  21. 2026-08-26 14:42 UTCEPSS rescore
  22. 2026-08-25 13:45 UTCEPSS rescore
  23. 2026-08-21 23:45 UTCEPSS rescore
  24. 2026-08-20 22:52 UTCEPSS rescore
  25. 2026-08-20 12:01 UTCOSV refresh
Show 75 more
  1. 2026-08-19 17:00 UTCEPSS rescore
  2. 2026-08-18 13:44 UTCEPSS rescore
  3. 2026-08-17 13:43 UTCEPSS rescore
  4. 2026-08-16 14:52 UTCEPSS rescore
  5. 2026-08-16 02:11 UTCEPSS rescore
  6. 2026-08-15 01:26 UTCEPSS rescore
  7. 2026-08-13 21:57 UTCEPSS rescore
  8. 2026-08-12 13:47 UTCEPSS rescore
  9. 2026-08-09 13:43 UTCEPSS rescore
  10. 2026-08-08 16:33 UTCEPSS rescore
  11. 2026-08-07 16:23 UTCEPSS rescore
  12. 2026-08-06 13:43 UTCEPSS rescore
  13. 2026-08-05 07:40 UTCOSV refresh
  14. 2026-08-04 15:06 UTCEPSS rescore
  15. 2026-08-04 10:34 UTCEPSS rescore
  16. 2026-08-02 02:23 UTCEPSS rescore
  17. 2026-08-01 04:12 UTCEPSS rescore
  18. 2026-07-30 16:25 UTCEPSS rescore
  19. 2026-07-30 01:27 UTCEPSS rescore
  20. 2026-07-28 15:33 UTCEPSS rescore
  21. 2026-07-26 14:51 UTCEPSS rescore
  22. 2026-07-25 14:15 UTCEPSS rescore
  23. 2026-07-24 14:14 UTCEPSS rescore
  24. 2026-07-23 14:15 UTCEPSS rescore
  25. 2026-07-23 14:15 UTCEPSS rescore
  26. 2026-07-23 01:53 UTCEG score recompute
  27. 2026-07-22 22:39 UTCEG score recompute
  28. 2026-07-22 14:05 UTCEPSS rescore
  29. 2026-07-21 15:22 UTCEPSS rescore
  30. 2026-07-21 15:22 UTCEPSS rescore
  31. 2026-07-20 17:04 UTCEPSS rescore
  32. 2026-07-20 17:04 UTCEPSS rescore
  33. 2026-07-19 14:28 UTCEPSS rescore
  34. 2026-07-19 14:28 UTCEPSS rescore
  35. 2026-07-19 06:22 UTCOSV refresh
  36. 2026-07-19 02:26 UTCEPSS rescore
  37. 2026-07-19 02:26 UTCEPSS rescore
  38. 2026-07-16 16:59 UTCEPSS rescore
  39. 2026-07-15 16:55 UTCEPSS rescore
  40. 2026-07-15 16:55 UTCEPSS rescore
  41. 2026-07-15 01:57 UTCEPSS rescore
  42. 2026-07-13 22:27 UTCEPSS rescore
  43. 2026-07-13 22:27 UTCEPSS rescore
  44. 2026-07-13 06:10 UTCEPSS rescore
  45. 2026-07-13 06:10 UTCEPSS rescore
  46. 2026-07-12 05:44 UTCEPSS rescore
  47. 2026-07-11 08:25 UTCEPSS rescore
  48. 2026-07-11 08:25 UTCEPSS rescore
  49. 2026-07-09 19:07 UTCEPSS rescore
  50. 2026-07-08 15:12 UTCEPSS rescore
  51. 2026-07-07 13:43 UTCEPSS rescore
  52. 2026-07-06 16:25 UTCEPSS rescore
  53. 2026-07-06 16:25 UTCEPSS rescore
  54. 2026-07-06 02:21 UTCEPSS rescore
  55. 2026-07-06 02:21 UTCEPSS rescore
  56. 2026-07-04 06:29 UTCEPSS rescore
  57. 2026-07-04 06:29 UTCEPSS rescore
  58. 2026-07-01 12:21 UTCOSV refresh
  59. 2026-06-30 23:20 UTCEPSS rescore
  60. 2026-06-30 23:20 UTCEPSS rescore
  61. 2026-06-29 14:04 UTCEPSS rescore
  62. 2026-06-28 04:54 UTCEPSS rescore
  63. 2026-06-28 04:54 UTCEPSS rescore
  64. 2026-06-27 03:06 UTCEPSS rescore
  65. 2026-06-27 03:06 UTCEPSS rescore
  66. 2026-06-25 13:48 UTCEPSS rescore
  67. 2026-06-24 14:03 UTCEPSS rescore
  68. 2026-06-24 14:03 UTCEPSS rescore
  69. 2026-06-23 21:31 UTCEPSS rescore
  70. 2026-06-23 21:31 UTCEPSS rescore
  71. 2026-06-22 14:23 UTCEPSS rescore
  72. 2026-06-22 14:23 UTCEPSS rescore
  73. 2026-06-21 14:54 UTCEPSS rescore
  74. 2026-06-21 14:54 UTCEPSS rescore
  75. 2026-06-21 01:57 UTCEPSS rescore

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2020-3702?
CVE-2020-3702 is a medium vulnerability published on September 8, 2020. 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,…
When was CVE-2020-3702 disclosed?
CVE-2020-3702 was first published in the National Vulnerability Database on September 8, 2020, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2020-3702 actively exploited?
CVE-2020-3702 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 72.1% of all scored CVEs.
What is the CVSS score of CVE-2020-3702?
CVE-2020-3702 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2020-3702?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2020-3702, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2020-3702

Explore →

Is Your Infrastructure Affected by CVE-2020-3702?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs