CVE-2024-30410
6.9
Vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:N/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XShow more
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:N/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XShow less
Source: sirt@juniper.net (Secondary)
Description
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.
Affected (43)
Configuration A
| Vulnerable Software | Affected Versions |
|---|---|
| Before 20.4 |
| Running on/with | Platform Versions |
|---|---|
Juniper Ex4300 | All versions |
Juniper Ex4300 24p | All versions |
Juniper Ex4300 24p S | All versions |
Juniper Ex4300 24t | All versions |
Juniper Ex4300 24t S | All versions |
Juniper Ex4300 32f | All versions |
Juniper Ex4300 32f Dc | All versions |
Juniper Ex4300 32f S | All versions |
Juniper Ex4300 48mp | All versions |
Juniper Ex4300 48mp S | All versions |
Juniper Ex4300 48p | All versions |
Juniper Ex4300 48p S | All versions |
Juniper Ex4300 48t | All versions |
Juniper Ex4300 48t Afi | All versions |
Juniper Ex4300 48t Dc | All versions |
Juniper Ex4300 48t Dc Afi | All versions |
Juniper Ex4300 48t S | All versions |
References (4)
Source: sirt@juniper.net
Issue Tracking
Source: af854a3a-2127-422b-91ae-364da2661108
Vendor Advisory
Source: af854a3a-2127-422b-91ae-364da2661108
Issue Tracking
Timeline
No history available yet.