When the same family inet or inet6 filter is applied on an IRB interface and on a physical interface as egress filter on EX4100, EX4400, EX4650 and QFX5120 devices, only one of the two filters will be applied, which can lead to traffic being sent out one of these interfaces which should have been blocked.
This issue affects Junos OS on EX Series and QFX Series:
* 23.4 version 23.4R2-S6,
* 24.2 version 24.2R2-S3.
No other Junos OS versions are affected.
Project Subscriptions
| Vendors | Products |
|---|---|
|
Juniper
Subscribe
|
Ex2300
Subscribe
Ex2300-c
Subscribe
Ex3400
Subscribe
Ex4000
Subscribe
Ex4100
Subscribe
Ex4100-f
Subscribe
Ex4100-h
Subscribe
Ex4300
Subscribe
Ex4400
Subscribe
Ex4600
Subscribe
Ex4650
Subscribe
Ex9204
Subscribe
Ex9208
Subscribe
Ex9214
Subscribe
Junos
Subscribe
Qfx10008
Subscribe
Qfx10016
Subscribe
Qfx5110
Subscribe
Qfx5120
Subscribe
Qfx5130
Subscribe
Qfx5200
Subscribe
Qfx5210
Subscribe
Qfx5220
Subscribe
Qfx5230-64cd
Subscribe
Qfx5240
Subscribe
Qfx5241
Subscribe
Qfx5700
Subscribe
|
|
Juniper Networks
Subscribe
|
Junos Os
Subscribe
|
No advisories yet.
Solution
The following software releases have been updated to resolve this specific issue: 23.4R2-S7, 24.2R2-S4.
Workaround
Two different workarounds are available: 1. create the same filter but under a different name and apply that to one of the interfaces, so that each interface has a unique copy of the filter in question as shown in the following example: user@host# copy ... <filter> to ... <filter2> user@host# set interfaces irb unit <unit2> family inet/inet6 filter output <filter2> 2. configure the filter as "interface specific" by adding the keyword to the filter definition: [ firewall family inet/inet6 filter <filter> interface-specific ] which implicitly creates a copy of the original filter per applied interface.
| Link | Providers |
|---|---|
| https://kb.juniper.net/JSA107815 |
|
Fri, 17 Apr 2026 18:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Juniper
Juniper ex2300 Juniper ex2300-c Juniper ex3400 Juniper ex4000 Juniper ex4100 Juniper ex4100-f Juniper ex4100-h Juniper ex4300 Juniper ex4400 Juniper ex4600 Juniper ex4650 Juniper ex9204 Juniper ex9208 Juniper ex9214 Juniper junos Juniper qfx10008 Juniper qfx10016 Juniper qfx5110 Juniper qfx5120 Juniper qfx5130 Juniper qfx5200 Juniper qfx5210 Juniper qfx5220 Juniper qfx5230-64cd Juniper qfx5240 Juniper qfx5241 Juniper qfx5700 |
|
| Weaknesses | NVD-CWE-Other | |
| CPEs | cpe:2.3:h:juniper:ex2300-c:-:*:*:*:*:*:*:* cpe:2.3:h:juniper:ex2300:-:*:*:*:*:*:*:* cpe:2.3:h:juniper:ex3400:-:*:*:*:*:*:*:* cpe:2.3:h:juniper:ex4000:-:*:*:*:*:*:*:* cpe:2.3:h:juniper:ex4100-f:-:*:*:*:*:*:*:* cpe:2.3:h:juniper:ex4100-h:-:*:*:*:*:*:*:* cpe:2.3:h:juniper:ex4100:-:*:*:*:*:*:*:* cpe:2.3:h:juniper:ex4300:-:*:*:*:*:*:*:* cpe:2.3:h:juniper:ex4400:-:*:*:*:*:*:*:* cpe:2.3:h:juniper:ex4600:-:*:*:*:*:*:*:* cpe:2.3:h:juniper:ex4650:-:*:*:*:*:*:*:* cpe:2.3:h:juniper:ex9204:-:*:*:*:*:*:*:* cpe:2.3:h:juniper:ex9208:-:*:*:*:*:*:*:* cpe:2.3:h:juniper:ex9214:-:*:*:*:*:*:*:* cpe:2.3:h:juniper:qfx10008:-:*:*:*:*:*:*:* cpe:2.3:h:juniper:qfx10016:-:*:*:*:*:*:*:* cpe:2.3:h:juniper:qfx5110:-:*:*:*:*:*:*:* cpe:2.3:h:juniper:qfx5120:-:*:*:*:*:*:*:* cpe:2.3:h:juniper:qfx5130:-:*:*:*:*:*:*:* cpe:2.3:h:juniper:qfx5200:-:*:*:*:*:*:*:* cpe:2.3:h:juniper:qfx5210:-:*:*:*:*:*:*:* cpe:2.3:h:juniper:qfx5220:-:*:*:*:*:*:*:* cpe:2.3:h:juniper:qfx5230-64cd:-:*:*:*:*:*:*:* cpe:2.3:h:juniper:qfx5240:-:*:*:*:*:*:*:* cpe:2.3:h:juniper:qfx5241:-:*:*:*:*:*:*:* cpe:2.3:h:juniper:qfx5700:-:*:*:*:*:*:*:* cpe:2.3:o:juniper:junos:23.4:r2-s6:*:*:*:*:*:* cpe:2.3:o:juniper:junos:24.2:r2-s3:*:*:*:*:*:* |
|
| Vendors & Products |
Juniper
Juniper ex2300 Juniper ex2300-c Juniper ex3400 Juniper ex4000 Juniper ex4100 Juniper ex4100-f Juniper ex4100-h Juniper ex4300 Juniper ex4400 Juniper ex4600 Juniper ex4650 Juniper ex9204 Juniper ex9208 Juniper ex9214 Juniper junos Juniper qfx10008 Juniper qfx10016 Juniper qfx5110 Juniper qfx5120 Juniper qfx5130 Juniper qfx5200 Juniper qfx5210 Juniper qfx5220 Juniper qfx5230-64cd Juniper qfx5240 Juniper qfx5241 Juniper qfx5700 |
Mon, 13 Apr 2026 18:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Fri, 10 Apr 2026 09:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Juniper Networks
Juniper Networks junos Os |
|
| Vendors & Products |
Juniper Networks
Juniper Networks junos Os |
Thu, 09 Apr 2026 21:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | An Incorrect Initialization of Resource vulnerability in the packet forwarding engine (pfe) of Juniper Networks Junos OS on specific EX Series and QFX Series device allows an unauthenticated, network-based attacker to cause an integrity impact to downstream networks. When the same family inet or inet6 filter is applied on an IRB interface and on a physical interface as egress filter on EX4100, EX4400, EX4650 and QFX5120 devices, only one of the two filters will be applied, which can lead to traffic being sent out one of these interfaces which should have been blocked. This issue affects Junos OS on EX Series and QFX Series: * 23.4 version 23.4R2-S6, * 24.2 version 24.2R2-S3. No other Junos OS versions are affected. | |
| Title | Junos OS: EX Series, QFX Series: If the same egress filter is configured on both an IRB and a physical interface one of those is not applied | |
| Weaknesses | CWE-1419 | |
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: juniper
Published:
Updated: 2026-04-13T18:06:20.091Z
Reserved: 2026-03-23T19:46:13.668Z
Link: CVE-2026-33773
Updated: 2026-04-13T17:58:44.055Z
Status : Analyzed
Published: 2026-04-09T22:16:25.590
Modified: 2026-04-17T17:56:54.663
Link: CVE-2026-33773
No data.
OpenCVE Enrichment
Updated: 2026-04-18T17:30:05Z