Junos OS Evolved: Connection limits is not being enforced while the resp. rate limit is being enforced
- 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-S4-EVO, 22.1R3-S3-EVO, 22.2R3-S2-EVO
- 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 Restriction of Excessive Authentication Attempts vulnerability in Juniper Networks Junos OS Evolved allows an unauthenticated, network-based attacker to cause a limited Denial of Service (DoS) to the management plane. When an incoming connection was blocked because it exceeded the connections-per-second rate-limit, the system doesn't consider existing connections anymore for subsequent connection attempts so that the connection limit can be exceeded. This issue affects Junos OS Evolved: • All versions before 21.4R3-S4-EVO, • 22.1-EVO versions before 22.1R3-S3-EVO, • 22.2-EVO versions before 22.2R3-S2-EVO, • 22.3-EVO versions before 22.3R2-S1-EVO, 22.3R3-EVO.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Juniper Networks Junos OS Evolved
fixed in 21.4R3-S4-EVO; From 22.1-EVO · fixed in 22.1R3-S3-EVO; From 22.2-EVO · fixed in 22.2R3-S2-EVO