Junos OS: jdhcpd will hang on receiving a specific DHCP packet
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 20.4R3-S9, 21.2R3-S7, 21.3R3-S5, 21.4R3-S5, 22.1R3-S4, and 3 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
An Improper Check for Unusual or Exceptional Conditions vulnerability in Juniper DHCP Daemon (jdhcpd) of Juniper Networks Junos OS allows an adjacent, unauthenticated attacker to cause the jdhcpd to consume all the CPU cycles resulting in a Denial of Service (DoS). On Junos OS devices with forward-snooped-client configured, if an attacker sends a specific DHCP packet to a non-configured interface, this will cause an infinite loop. The DHCP process will have to be restarted to recover the service. This issue affects: Juniper Networks Junos OS • All versions earlier than 20.4R3-S9; • 21.2 versions earlier than 21.2R3-S7; • 21.3 versions earlier than 21.3R3-S5; • 21.4 versions earlier than 21.4R3-S5; • 22.1 versions earlier than 22.1R3-S4; • 22.2 versions earlier than 22.2R3-S3; • 22.3 versions earlier than 22.3R3-S2; • 22.4 versions earlier than 22.4R2-S2, 22.4R3; • 23.2 versions earlier than 23.2R2.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Juniper Networks Junos OS
fixed in 20.4R3-S9; From 21.2 · fixed in 21.2R3-S7; From 21.3 · fixed in 21.3R3-S5; From 21.4 · fixed in 21.4R3-S5; From 22.1 · fixed in 22.1R3-S4; From 22.2 · fixed in 22.2R3-S3; From 22.3 · fixed in 22.3R3-S2; From 23.2 · fixed in 23.2R2