Junos OS: Due to a race condition AgentD process causes a memory corruption and FPC reset
- 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 21.4R3-S9, 22.2R3-S5, 22.3R3-S4, 22.4R3-S3, 23.2R2-S2, 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
A Time-of-check Time-of-use (TOCTOU) Race Condition vulnerability in the AgentD process of Juniper Networks Junos OS allows an attacker who is already causing impact to established sessions which generates counter changes picked up by the AgentD process during telemetry polling, to move the AgentD process into a state where AgentD attempts to reap an already destroyed sensor. This reaping attempt then leads to memory corruption causing the FPC to crash which is a Denial of Service (DoS). The FPC will recover automatically without user intervention after the crash. This issue affects Junos OS: • All versions before 21.4R3-S9 • From 22.2 before 22.2R3-S5, • From 22.3 before 22.3R3-S4, • From 22.4 before 22.4R3-S3, • From 23.2 before 23.2R2-S2, • From 23.4 before 23.4R2. This issue does not affect Junos OS Evolved.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Juniper Networks Junos OS
fixed in 21.4R3-S9; From 22.2 · fixed in 22.2R3-S5; From 22.3 · fixed in 22.3R3-S4; From 22.4 · fixed in 22.4R3-S3; From 23.2 · fixed in 23.2R2-S2; From 23.4 · fixed in 23.4R2