Junos OS: MX Series: Malformed SyncE or PTP clock input causes continuous RE switchover
- 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 23.2R2-S7.7, 23.4R2-S8.13, 24.2R2-S5.5, 24.4R2-S4, 25.2R2-S1, and 1 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 Resource Locking vulnerability in the clock synchronization daemon (clksyncd) of Juniper Networks Junos OS on MX Series allows a unauthenticated, logically adjacent attacker to cause a Denial-of-Service (DoS). If a SyncE or PTP upstream node sends a malformed message to an MX device equipped with SCBE3, a false 19.44MHz alarm is generated on the master RE. This leads to persistent RE switchovers and a clksyncd process crash. This issue is outside the attacker's direct control as it's a race condition. This issue affects Junos OS on MX Series: • All versions before 23.2R2-S7.7; • 23.4 versions before 23.4R2-S8.13; • 24.2 versions before 24.2R2-S5.5; • 24.4 versions before 24.4R2-S4; • 25.2 versions before 25.2R2-S1; • 25.4 versions before 25.4R1-S2.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Juniper Networks Junos OS
fixed in 23.2R2-S7.7; From 23.4 · fixed in 23.4R2-S8.13; From 24.2 · fixed in 24.2R2-S5.5; From 24.4 · fixed in 24.4R2-S4; From 25.2 · fixed in 25.2R2-S1; From 25.4 · fixed in 25.4R1-S2