CVE-2023-28975

MEDIUMNVD 4.64.6
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 4.6 from GitHub Security Advisory published 2023-04-18. NVD baseline CVSS 4.6; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
4.6EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 4.6Exploit: None knownExposed services: Not assessed

The following software releases have been updated to resolve this specific issue: 19.4R3-S10, 20.2R3-S7, 20.3R3-S6, 20.4R3-S5, 21.1R3-S4, 21.2R3-S4, 21.3R3-S3, 21.4R3-S2, 22.1R2-S2, 22.1R3, 22.2R2, 22.3R1-S1, 22.3R2, 22… (from the CVE record's solution, Juniper Networks, Inc.) — apply it.

An Unexpected Status Code or Return Value vulnerability in the kernel of Juniper Networks Junos OS allows an unauthenticated attacker with physical access to the device to cause a Denial of Service (DoS). When certain USB devices are connected to a USB port of the routing-engine (RE), the kernel will crash leading to a reboot of the device. The device will continue to crash as long as the USB device is connected. This issue affects Juniper Networks Junos OS: All versions prior to 19.4R3-S10; 20.2 versions prior to 20.2R3-S7; 20.3 versions prior to 20.3R3-S6; 20.4 versions prior to 20.4R3-S5; 21.1 versions prior to 21.1R3-S4; 21.2 versions prior to 21.2R3-S4; 21.3 versions prior to 21.3R3-S3; 21.4 versions prior to 21.4R3-S2; 22.1 versions prior to 22.1R2-S2, 22.1R3; 22.2 versions prior to 22.2R2, 22.2R3; 22.3 versions prior to 22.3R1-S1, 22.3R2; 22.4 versions prior to 22.4R2.

CVSS v3
4.6
EG Score
4.6MEDIUMmedium confidence
EG Risk
21
EG Risk 21/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity46% × 45%
Impact severity (EG Severity): CVSS 4.6 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: The following software releases have been updated to resolve this specific issue: 19.4R3-S10, 20.2R3-S7, 20.3R3-S6, 20.4R3-S5, 21.1R3-S4, 21.2R3-S4, 21.3R3-S3, 21.4R3-S2, 22.1R2-S2, 22.1R3, 22.2R2, 22.3R1-S1, 22.3R2, 22… (from the CVE record's solution, Juniper Networks, Inc.). Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
20th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (4.6): severity, escalated by confirmed exploitation. This CVE's 4.6 is its impact severity (EG Severity), not escalated.

EG Severity
4.6 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-17). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

The following software releases have been updated to resolve this specific issue: 19.4R3-S10, 20.2R3-S7, 20.3R3-S6, 20.4R3-S5, 21.1R3-S4, 21.2R3-S4, 21.3R3-S3, 21.4R3-S2, 22.1R2-S2, 22.1R3, 22.2R2, 22.3R1-S1, 22.3R2, 22… (from the CVE record's solution, Juniper Networks, Inc.). Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

April 17, 2023

Last Modified

November 21, 2024

References (1)

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 33× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 91 of 188 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 9 repeat rows among the latest 100 are merged into the row they repeat. The 97 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2023-28975?
CVE-2023-28975 is a medium-severity vulnerability; its CVE record was published on April 17, 2023. An Unexpected Status Code or Return Value vulnerability in the kernel of Juniper Networks Junos OS allows an unauthenticated attacker with physical access to the device to cause a Denial of Service (DoS). When certain USB devices are connected to a USB port of the routing-engine (RE), the kernel…
When was CVE-2023-28975 made public?
CVE-2023-28975 was made public on April 12, 2023: that is the date its CVE record's CNA, Juniper Networks, Inc., gives for when the vulnerability was made public. The CVE record itself was published on April 17, 2023. EchelonGraph's copy of the record carries a last-modified date of November 21, 2024; the record at its source may have been updated since.
Is CVE-2023-28975 actively exploited?
CVE-2023-28975 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (20th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-28975?
CVE-2023-28975 has a CVSS v3 base score of 4.6 (NVD).
How do I remediate CVE-2023-28975?
The CVE record's solution for CVE-2023-28975, written by its CNA Juniper Networks, Inc., names the fix: "The following software releases have been updated to resolve this specific issue: 19.4R3-S10, 20.2R3-S7, 20.3R3-S6, 20.4R3-S5, 21.1R3-S4, 21.2R3-S4, 21.3R3-S3, 21.4R3-S2, 22.1R2-S2, 22.1R3, 22.2R2, 22.3R1-S1, 22.3R2, 22…"

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2023-28975

Explore →

Is Your Infrastructure Affected by CVE-2023-28975?

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

Book a Demo →Browse All CVEs