Skip to main content
Vulnerability Database/CVE-2024-30410

CVE-2024-30410: Juniper Junos EX4300 Firewall Bypass Flaw

CVE-2024-30410 is an information disclosure vulnerability affecting Juniper Junos OS on EX4300 Series switches, allowing IPv6 traffic to bypass lo0 firewall filters and reach the routing engine. This article covers technical details, affected versions, security impact, and mitigation strategies.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2024-30410 Overview

CVE-2024-30410 is an Incorrect Behavior Order vulnerability [CWE-696] in the routing engine (RE) of Juniper Networks Junos OS on EX4300 Series switches. The flaw causes IPv6 traffic destined for the device to reach the RE instead of being discarded when a discard term is configured on the loopback (lo0) interface firewall filter. The intended behavior is that the lo0 firewall filter takes precedence over the revenue interface firewall filter. This issue affects only IPv6 firewall filters on the EX4300 switch and no other Juniper platforms.

Critical Impact

Attackers can send IPv6 traffic directly to the routing engine despite explicit discard filter rules, undermining control-plane protection and enabling partial denial-of-service or reconnaissance against the device.

Affected Products

  • Juniper Networks Junos OS on EX4300 Series: all versions before 20.4R3-S10
  • Juniper Networks Junos OS on EX4300 Series: 21.2 versions before 21.2R3-S7
  • Juniper Networks Junos OS on EX4300 Series: 21.4 versions before 21.4R3-S6

Discovery Timeline

  • 2024-04-12 - CVE-2024-30410 published to NVD
  • 2026-06-17 - Last updated in NVD database

Technical Details for CVE-2024-30410

Vulnerability Analysis

The vulnerability stems from an incorrect ordering of firewall filter evaluation on EX4300 switches. Junos OS is designed to apply the loopback interface (lo0) firewall filter before any revenue interface filters for host-bound traffic. On EX4300 hardware running affected releases, this precedence is not enforced for IPv6 filters. Traffic that an administrator explicitly marked for discard via the lo0 IPv6 filter still reaches the routing engine. Operators relying on lo0 filters as their primary control-plane protection mechanism therefore have an incomplete defense against IPv6-based reconnaissance and resource-consumption attacks aimed at the RE.

Root Cause

The root cause is classified as CWE-696 (Incorrect Behavior Order). The filter evaluation pipeline on the EX4300 processes IPv6 host-bound packets in an order that bypasses the intended lo0 discard logic. This is a platform-specific defect limited to the EX4300 switch family. IPv4 firewall filters are not affected, and no other Juniper products exhibit this behavior.

Attack Vector

Exploitation requires only network reachability to the device over IPv6. No authentication, user interaction, or special privileges are needed. An unauthenticated remote attacker sends IPv6 packets whose destination matches a term that should be discarded by the lo0 firewall filter. Because the filter ordering is incorrect, those packets reach the routing engine and are processed by control-plane services. This weakens the device's security posture by allowing targeted probing of RE-hosted services and increasing exposure to control-plane resource exhaustion. No arbitrary code execution or data disclosure results directly from the flaw.

No verified public proof-of-concept code is available. Refer to the Juniper Security Advisory JSA79100 for vendor-specific technical detail.

Detection Methods for CVE-2024-30410

Indicators of Compromise

  • Unexpected IPv6 traffic observed on routing engine interfaces that should have been filtered by lo0 discard terms
  • Elevated control-plane CPU utilization on EX4300 switches correlating with IPv6 probing from untrusted sources
  • Firewall filter counters on revenue interfaces incrementing for IPv6 packets destined to the device loopback addresses

Detection Strategies

  • Audit EX4300 devices running Junos OS versions earlier than 20.4R3-S10, 21.2R3-S7, or 21.4R3-S6 for the presence of IPv6 lo0 firewall filters with discard terms
  • Compare expected versus actual filter hit counts using show firewall filter <name> to confirm whether discard terms are being honored for IPv6
  • Deploy network flow analysis to identify IPv6 flows terminating at the RE that match discard criteria

Monitoring Recommendations

  • Monitor RE CPU, memory, and session table metrics for anomalies on EX4300 platforms
  • Enable logging on IPv6 lo0 filter terms and alert on traffic that should have been dropped but was accepted
  • Correlate control-plane protocol activity (SSH, SNMP, NTP over IPv6) with upstream ACL and IPv6 flow telemetry to detect bypassed filter conditions

How to Mitigate CVE-2024-30410

Immediate Actions Required

  • Upgrade affected EX4300 switches to Junos OS 20.4R3-S10, 21.2R3-S7, 21.4R3-S6, or later fixed releases
  • Inventory all EX4300 devices and identify any that rely on IPv6 lo0 firewall filters for RE protection
  • Apply compensating IPv6 access controls at upstream devices until patching is complete

Patch Information

Juniper Networks has published fixes in Junos OS 20.4R3-S10, 21.2R3-S7, and 21.4R3-S6, as well as all subsequent releases. See the Juniper Security Advisory JSA79100 for the complete list of fixed versions and upgrade guidance.

Workarounds

  • Apply IPv6 discard terms directly on revenue interface input firewall filters rather than relying solely on lo0 filter precedence
  • Restrict IPv6 reachability to the EX4300 management and loopback addresses using upstream router ACLs or infrastructure ACLs
  • Disable unused IPv6 control-plane services on the EX4300 to reduce RE attack surface until the patch is applied
bash
# Example: apply IPv6 discard filter on revenue interface as workaround
set firewall family inet6 filter PROTECT-RE term BLOCK-TO-RE from destination-address <device-ipv6>/128
set firewall family inet6 filter PROTECT-RE term BLOCK-TO-RE then discard
set interfaces <revenue-ifl> unit 0 family inet6 filter input PROTECT-RE
commit

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.