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-30389 Overview
CVE-2024-30389 is an Incorrect Behavior Order vulnerability [CWE-696] in the Packet Forwarding Engine (PFE) of Juniper Networks Junos OS on EX4300 Series switches. When an output firewall filter is applied to an interface, the PFE fails to recognize matching packets and instead permits all traffic. This allows an unauthenticated, network-based attacker to bypass intended egress filtering and impact the integrity of networks downstream of the affected device.
The issue affects Junos OS 21.4 releases from 21.4R1 and earlier than 21.4R3-S6. Releases earlier than 21.4R1 are not affected.
Critical Impact
Output firewall filters silently fail on EX4300 Series devices, permitting unauthorized traffic to pass through and reach downstream networks that administrators believe are protected.
Affected Products
- Juniper Junos OS 21.4 releases from 21.4R1 to before 21.4R3-S6
- Juniper EX4300 Series switches (EX4300-24P/24T, EX4300-32F, EX4300-48MP, EX4300-48P, EX4300-48T and associated -S, -DC, and -AFI variants)
- Deployments relying on egress firewall filters for traffic segmentation
Discovery Timeline
- 2024-04-12 - CVE-2024-30389 published to NVD
- 2026-06-17 - Last updated in NVD database
Technical Details for CVE-2024-30389
Vulnerability Analysis
The vulnerability resides in the Packet Forwarding Engine (PFE), the hardware-accelerated data plane responsible for applying firewall filters at line rate. On affected Junos OS 21.4 builds running on EX4300 Series switches, the PFE processes output firewall filters in an incorrect order. It evaluates traffic against the interface but does not correctly match packets against the configured filter terms.
The practical outcome is a default-permit behavior on egress. Operators who configure explicit deny terms, logging rules, or policer actions on an output filter will see those actions bypassed. Traffic that should be blocked, counted, or rate-limited is instead forwarded unchanged toward downstream networks.
Because the flaw occurs in the PFE rather than the control plane, there is no error log or configuration failure to warn operators. The filter appears to be committed and active while silently failing.
Root Cause
The root cause is classified under [CWE-696] (Incorrect Behavior Order). The PFE applies the sequence of filter evaluation steps in an order that prevents matching logic from executing against output traffic on EX4300 hardware. This regression was introduced in the 21.4R1 release train and remained present through 21.4R3-S5.
Attack Vector
The attack vector is network-based and requires no authentication or user interaction. An attacker on a connected network segment can send traffic that would normally be denied by an egress filter. Because the PFE permits the traffic regardless of filter configuration, the attacker reaches downstream hosts that defenders assumed were protected by the EX4300 enforcement point.
No exploit code is required. The vulnerability is triggered simply by the device forwarding traffic through an interface with an output filter applied. There is no public proof-of-concept and the vulnerability is not listed in the CISA Known Exploited Vulnerabilities catalog.
No verified code examples are available for this vulnerability. See the Juniper Security Advisory JSA79185 for vendor technical details.
Detection Methods for CVE-2024-30389
Indicators of Compromise
- Downstream hosts receiving traffic from source addresses or protocols that an output firewall filter on an EX4300 should block.
- Firewall filter counters (show firewall filter <name>) that remain at zero despite expected matching traffic on the interface.
- Unexpected flows observed in NetFlow, sFlow, or packet captures taken downstream of an EX4300 egress interface.
Detection Strategies
- Audit all EX4300 Series devices for Junos OS versions between 21.4R1 and 21.4R3-S5 using show version.
- Enumerate interfaces with output firewall filters applied and validate enforcement using active test traffic against each deny term.
- Compare pre-filter and post-filter traffic captures to confirm whether configured deny or policer actions are taking effect.
Monitoring Recommendations
- Continuously poll firewall filter counters via SNMP or Junos telemetry and alert when expected deny counters remain static over time.
- Ingest flow data from EX4300 egress interfaces into a SIEM or data lake and alert on traffic patterns that violate documented egress policy.
- Monitor Juniper advisory feeds for updates related to JSA79185 and the EX4300 PFE.
How to Mitigate CVE-2024-30389
Immediate Actions Required
- Inventory all EX4300 Series switches running Junos OS 21.4 and prioritize upgrade of devices enforcing egress security policy.
- Upgrade affected devices to Junos OS 21.4R3-S6 or later, or move to a release train not affected by this issue.
- Validate egress enforcement after upgrade by injecting test traffic that matches each deny term and confirming counter increments.
Patch Information
Juniper has released a fix in Junos OS 21.4R3-S6 and later. Full details, including applicable release trains and upgrade guidance, are published in the Juniper Security Advisory JSA79185. Releases earlier than 21.4R1 are not affected and do not require action for this CVE.
Workarounds
- Where upgrade is not immediately feasible, enforce the equivalent policy as an input firewall filter on the receiving interface of an adjacent device.
- Apply input firewall filters on the EX4300 itself to catch traffic before it reaches the broken egress enforcement path.
- Use upstream or downstream devices with equivalent filtering capability as a compensating control until the patched Junos release is deployed.
# Example: verify Junos version and inspect output firewall filter counters
show version | match Junos
show configuration interfaces | display set | match "filter output"
show firewall filter <output-filter-name>
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

