CVE-2023-28975

Persistent reboot via mishandled USB device response

Published Apr 17, 2023 · Updated Feb 5, 2025

Unexpected return-value handling in Juniper Networks Junos OS allows physically proximate attackers to reboot routing engines via USB. The kernel mishandles a status or return value while enumerating certain USB devices connected to a routing-engine port, causing it to crash. Physical access is required, and the routing engine repeatedly crashes and reboots for as long as the device remains connected.

CVSS severity4.6
Medium
EPSS probability0.29%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Unexpected return-value handling in Juniper Networks Junos OS allows physically proximate attackers to reboot routing engines via USB. The kernel mishandles a status or return value while enumerating certain USB devices connected to a routing-engine port, causing it to crash. Physical access is required, and the routing engine repeatedly crashes and reboots for as long as the device remains connected.

The record

CVE
CVE-2023-28975
Published
Apr 17, 2023
Updated
Feb 5, 2025
Vendor
Juniper Networks
Product
Junos OS
Classifications
CWE-394, CWE-754, T1529
Attack vector
physical
Privileges
unauthenticated

Timeline

How it unfolded

  1. Apr 17, 2023CVE publishedPublication date reported by the CVE source.
  2. Feb 5, 2025Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=20.2 <20.2R3-S7
  2. Affected versionversion=20.3 <20.3R3-S6
  3. Affected versionversion=20.4 <20.4R3-S5
  4. Affected versionversion=21.1 <21.1R3-S4
  5. Affected versionversion=21.2 <21.2R3-S4
  6. Affected versionversion=21.3 <21.3R3-S3
  7. Affected versionversion=21.4 <21.4R3-S2
  8. Affected versionversion=22.1 <22.1R2-S2, 22.1R3
  9. Affected versionversion=22.2 <22.2R2
  10. Affected versionversion=22.3 <22.3R1-S1, 22.3R2
  11. Affected versionversion=22.4 <22.4R2
  12. Affected versionversion=unspecified <19.4R3-S10

What conditions does exploitation require?

Attack vectorphysical
Required privilegesunauthenticated

What is affected?

Juniper Networks · Junos OSversion=20.2 <20.2R3-S7; version=20.3 <20.3R3-S6; version=20.4 <20.4R3-S5; version=21.1 <21.1R3-S4; version=21.2 <21.2R3-S4; version=21.3 <21.3R3-S3; version=21.4 <21.4R3-S2; version=22.1 <22.1R2-S2, 22.1R3; version=22.2 <22.2R2; version=22.3 <22.3R1-S1, 22.3R2; version=22.4 <22.4R2; version=unspecified <19.4R3-S10

Published CVSS scores

4.6Juniper NetworksCVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorphysical
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-394Unexpected Status Code or Return Value
CWE-754Improper Check for Unusual or Exceptional Conditions
T1529System Shutdown/Reboot

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo