CVE-2020-4060

MEDIUMNVD 4.14.1—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 4.1 under NVD CVSS v3. EPSS exploit probability: 0.9% (59th percentile of EPSS-scored CVEs). 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
4.1EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.9%CVSS: 4.1Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

In LoRa Basics Station before 2.0.4, there is a Use After Free vulnerability that leads to memory corruption. This bug is triggered on 32-bit machines when the CUPS server responds with a message (https://doc.sm.tc/station/cupsproto.html#http-post-response) where the signature length is larger than 2 GByte (never happens in practice), or the response is crafted specifically to trigger this issue (i.e. the length signature field indicates a value larger than (2**31)-1 although the signature actually does not contain that much data). In such a scenario, on 32 bit machines, Basic Station would execute a code path, where a piece of memory is accessed after it has been freed, causing the process to crash and restarted again. The CUPS transaction is typically mutually authenticated over TLS. Therefore, in order to trigger this vulnerability, the attacker would have to gain access to the CUPS server first. If the user chose to operate without authentication over TLS but yet is concerned about this vulnerability, one possible workaround is to enable TLS authentication. This has been fixed in 2.0.4.

CVSS v3
4.1
EG Score
4.1MEDIUMmedium confidence
EG Risk
23
EG Risk 23/100CISA SSVC

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
Severity41% × 45%
Exploitation1% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.9%
EPSS %ILE
59th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

June 22, 2020

Last Modified

November 21, 2024

References (2)

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 27× 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 165 total refreshes for this CVE.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2020-4060?
CVE-2020-4060 is a medium vulnerability published on June 22, 2020. In LoRa Basics Station before 2.0.4, there is a Use After Free vulnerability that leads to memory corruption. This bug is triggered on 32-bit machines when the CUPS server responds with a message (https://doc.sm.tc/station/cupsproto.html#http-post-response) where the signature length is larger than…
When was CVE-2020-4060 disclosed?
CVE-2020-4060 was first published on June 22, 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-4060 actively exploited?
CVE-2020-4060 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.9% probability of exploitation in the next 30 days (59th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2020-4060?
CVE-2020-4060 has a CVSS v3 base score of 4.1 (NVD).
How do I remediate CVE-2020-4060?
No fix for CVE-2020-4060 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2020-4060

Explore →

Is Your Infrastructure Affected by CVE-2020-4060?

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

Book a Demo →Browse All CVEs