First published: Fri Apr 12 2024(Updated: )
An Incorrect Behavior Order in the routing engine (RE) of Juniper Networks Junos OS on EX4300 Series allows traffic intended to the device to reach the RE instead of being discarded when the discard term is set in loopback (lo0) interface. The intended function is that the lo0 firewall filter takes precedence over the revenue interface firewall filter. This issue affects only IPv6 firewall filter. This issue only affects the EX4300 switch. No other products or platforms are affected by this vulnerability. This issue affects Juniper Networks Junos OS: * All versions before 20.4R3-S10, * from 21.2 before 21.2R3-S7, * from 21.4 before 21.4R3-S6.
Credit: sirt@juniper.net
Affected Software | Affected Version | How to fix |
---|---|---|
Juniper Networks Junos OS | <20.4R3-S10>=undefined>=undefined | |
All of | ||
Any of | ||
Juniper JUNOS | <20.4 | |
Juniper JUNOS | =20.4 | |
Juniper JUNOS | =20.4-r1 | |
Juniper JUNOS | =20.4-r1-s1 | |
Juniper JUNOS | =20.4-r2 | |
Juniper JUNOS | =20.4-r2-s1 | |
Juniper JUNOS | =20.4-r2-s2 | |
Juniper JUNOS | =20.4-r3 | |
Juniper JUNOS | =20.4-r3-s1 | |
Juniper JUNOS | =20.4-r3-s2 | |
Juniper JUNOS | =20.4-r3-s3 | |
Juniper JUNOS | =20.4-r3-s4 | |
Juniper JUNOS | =20.4-r3-s5 | |
Juniper JUNOS | =20.4-r3-s6 | |
Juniper JUNOS | =20.4-r3-s7 | |
Juniper JUNOS | =20.4-r3-s8 | |
Juniper JUNOS | =20.4-r3-s9 | |
Juniper JUNOS | =21.2 | |
Juniper JUNOS | =21.2-r1 | |
Juniper JUNOS | =21.2-r1-s1 | |
Juniper JUNOS | =21.2-r1-s2 | |
Juniper JUNOS | =21.2-r2 | |
Juniper JUNOS | =21.2-r2-s1 | |
Juniper JUNOS | =21.2-r2-s2 | |
Juniper JUNOS | =21.2-r3 | |
Juniper JUNOS | =21.2-r3-s1 | |
Juniper JUNOS | =21.2-r3-s2 | |
Juniper JUNOS | =21.2-r3-s3 | |
Juniper JUNOS | =21.2-r3-s4 | |
Juniper JUNOS | =21.2-r3-s5 | |
Juniper JUNOS | =21.2-r3-s6 | |
Juniper JUNOS | =21.4-r1 | |
Juniper JUNOS | =21.4-r1-s1 | |
Juniper JUNOS | =21.4-r1-s2 | |
Juniper JUNOS | =21.4-r2 | |
Juniper JUNOS | =21.4-r2-s1 | |
Juniper JUNOS | =21.4-r2-s2 | |
Juniper JUNOS | =21.4-r3 | |
Juniper JUNOS | =21.4-r3-s1 | |
Juniper JUNOS | =21.4-r3-s2 | |
Juniper JUNOS | =21.4-r3-s3 | |
Juniper JUNOS | =21.4-r3-s4 | |
Juniper JUNOS | =21.4-r3-s5 | |
Any of | ||
Juniper EX4300 | ||
Juniper ex4300-24p | ||
Juniper ex4300-24p-s | ||
Juniper ex4300-24t | ||
Juniper ex4300-24t-s | ||
Juniper ex4300-32f | ||
Juniper ex4300-32f-dc | ||
Juniper ex4300-32f-s | ||
Juniper ex4300-48mp | ||
Juniper ex4300-48mp-s | ||
Juniper ex4300-48p | ||
Juniper ex4300-48p-s | ||
Juniper ex4300-48t | ||
Juniper ex4300-48t-afi | ||
Juniper ex4300-48t-dc | ||
Juniper ex4300-48t-dc-afi | ||
Juniper ex4300-48t-s |
The following software releases have been updated to resolve this specific issue: Junos OS: 20.4R3-S10, 21.2R3-S7, 21.4R3-S6, and all subsequent releases.
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-30410 has been classified with a medium severity due to its potential impact on network traffic management.
To mitigate CVE-2024-30410, update your Juniper Networks Junos OS to the latest version that addresses this vulnerability.
CVE-2024-30410 affects Juniper Networks Junos OS versions up to 20.4R3-S10 and specific versions in the 20.4 and 21.x series.
CVE-2024-30410 involves an incorrect behavior order in the routing engine that allows traffic to bypass intended firewall rules.
As of now, there are no documented workarounds for CVE-2024-30410, and applying the necessary updates is recommended.