First published: Fri Oct 16 2020(Updated: )
When configuring stateless firewall filters in Juniper Networks EX4600 and QFX 5000 Series devices using Virtual Extensible LAN protocol (VXLAN), the discard action will fail to discard traffic under certain conditions. Given a firewall filter configuration similar to: family ethernet-switching { filter L2-VLAN { term ALLOW { from { user-vlan-id 100; } then { accept; } } term NON-MATCH { then { discard; } } when there is only one term containing a 'user-vlan-id' match condition, and no other terms in the firewall filter except discard, the discard action for non-matching traffic will only discard traffic with the same VLAN ID specified under 'user-vlan-id'. Other traffic (e.g. VLAN ID 200) will not be discarded. This unexpected behavior can lead to unintended traffic passing through the interface where the firewall filter is applied. This issue only affects systems using VXLANs. This issue affects Juniper Networks Junos OS on QFX5K Series: 18.1 versions prior to 18.1R3-S7, except 18.1R3; 18.2 versions prior to 18.2R2-S7, 18.2R3-S1; 18.3 versions prior to 18.3R1-S5, 18.3R2-S4, 18.3R3; 18.4 versions prior to 18.4R1-S7, 18.4R2-S1, 18.4R3; 19.1 versions prior to 19.1R1-S5, 19.1R2; 19.2 versions prior to 19.2R1-S5, 19.2R2.
Credit: sirt@juniper.net
Affected Software | Affected Version | How to fix |
---|---|---|
Juniper JUNOS | =18.1 | |
Juniper JUNOS | =18.1-r1 | |
Juniper JUNOS | =18.1-r2 | |
Juniper JUNOS | =18.1-r2-s1 | |
Juniper JUNOS | =18.1-r2-s2 | |
Juniper JUNOS | =18.1-r2-s4 | |
Juniper JUNOS | =18.1-r3 | |
Juniper JUNOS | =18.1-r3-s1 | |
Juniper JUNOS | =18.1-r3-s2 | |
Juniper JUNOS | =18.1-r3-s3 | |
Juniper JUNOS | =18.1-r3-s4 | |
Juniper JUNOS | =18.1-r3-s6 | |
Juniper JUNOS | =18.2 | |
Juniper JUNOS | =18.2-r1 | |
Juniper JUNOS | =18.2-r1 | |
Juniper JUNOS | =18.2-r1-s3 | |
Juniper JUNOS | =18.2-r1-s4 | |
Juniper JUNOS | =18.2-r1-s5 | |
Juniper JUNOS | =18.2-r2 | |
Juniper JUNOS | =18.2-r2-s1 | |
Juniper JUNOS | =18.2-r2-s2 | |
Juniper JUNOS | =18.2-r2-s3 | |
Juniper JUNOS | =18.2-r2-s4 | |
Juniper JUNOS | =18.2-r2-s5 | |
Juniper JUNOS | =18.2-r2-s6 | |
Juniper JUNOS | =18.2-r3 | |
Juniper JUNOS | =18.3 | |
Juniper JUNOS | =18.3-r1 | |
Juniper JUNOS | =18.3-r1-s1 | |
Juniper JUNOS | =18.3-r1-s2 | |
Juniper JUNOS | =18.3-r1-s3 | |
Juniper JUNOS | =18.3-r1-s4 | |
Juniper JUNOS | =18.3-r2 | |
Juniper JUNOS | =18.3-r2-s1 | |
Juniper JUNOS | =18.3-r2-s2 | |
Juniper JUNOS | =18.3-r2-s3 | |
Juniper JUNOS | =18.4 | |
Juniper JUNOS | =18.4-r1 | |
Juniper JUNOS | =18.4-r1-s1 | |
Juniper JUNOS | =18.4-r1-s2 | |
Juniper JUNOS | =18.4-r1-s3 | |
Juniper JUNOS | =18.4-r1-s4 | |
Juniper JUNOS | =18.4-r1-s5 | |
Juniper JUNOS | =18.4-r1-s6 | |
Juniper JUNOS | =18.4-r2 | |
Juniper JUNOS | =19.1 | |
Juniper JUNOS | =19.1-r1 | |
Juniper JUNOS | =19.1-r1-s1 | |
Juniper JUNOS | =19.1-r1-s2 | |
Juniper JUNOS | =19.1-r1-s3 | |
Juniper JUNOS | =19.1-r1-s4 | |
Juniper JUNOS | =19.2 | |
Juniper JUNOS | =19.2-r1 | |
Juniper JUNOS | =19.2-r1-s1 | |
Juniper JUNOS | =19.2-r1-s2 | |
Juniper JUNOS | =19.2-r1-s3 | |
Juniper JUNOS | =19.2-r1-s4 | |
Juniper Qfx5100 | ||
Juniper Qfx5110 | ||
Juniper Qfx5120 | ||
Juniper Qfx5130 | ||
Juniper Qfx5200 | ||
Juniper Qfx5210 | ||
Juniper Qfx5220 |
The following software releases have been updated to resolve this specific issue: Junos OS 18.1R3-S7, 18.2R2-S7, 18.2R3-S1, 18.3R1-S5, 18.3R2-S4, 18.3R3, 18.4R1-S7, 18.4R2-S1, 18.4R3, 19.1R1-S5, 19.1R2, 19.2R1-S5, 19.2R2, 19.3R1, and all subsequent releases.
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.