rpd restart via unreleased socket-input memory
Published Jan 12, 2024 · Updated Jun 17, 2025
Memory leakage in rpd in Juniper Networks Junos OS and Junos OS Evolved allows remote attackers to crash and restart rpd. The daemon fails to release socket-input memory when BGP route churn updates next hops, causing allocations to accumulate until rpd restarts. The attack requires no authentication but only applies when jflow is configured with version-ipfix or version9, and it interrupts routing-protocol service.
Summary
What happened
Memory leakage in rpd in Juniper Networks Junos OS and Junos OS Evolved allows remote attackers to crash and restart rpd. The daemon fails to release socket-input memory when BGP route churn updates next hops, causing allocations to accumulate until rpd restarts. The attack requires no authentication but only applies when jflow is configured with version-ipfix or version9, and it interrupts routing-protocol service.
The record
- CVE
- CVE-2024-21611
- Published
- Jan 12, 2024
- Updated
- Jun 17, 2025
- Vendor
- Juniper Networks
- Product
- Junos OS Evolved
- Classifications
- CWE-401, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 12, 2024CVE publishedPublication date reported by the CVE source.
- Jun 17, 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.
- Affected versionversion=21.4-EVO <21.4R3-EVO
- Affected versionversion=22.1-EVO <22.1R3-EVO
- Affected versionversion=22.2-EVO <22.2R3-EVO
What conditions does exploitation require?
What is affected?
Published CVSS scores
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.
Weakness, pattern, technique
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