An Unsupported Feature in the UI vulnerability in Juniper Networks Junos OS on MX Series and EX9200 Series allows an unauthenticated, network-based attacker to cause partial impact to the integrity of the device.
If the "tcp-reset" option is added to the "reject" action in an IPv6 filter which matches on "payload-protocol", packets are permitted instead of rejected. This happens because the payload-protocol match criteria is not supported in the kernel filter causing it to accept all packets without taking any other action. As a fix the payload-protocol match will be treated the same as a "next-header" match to avoid this filter bypass.
This issue doesn't affect IPv4 firewall filters.
This issue affects Juniper Networks Junos OS on MX Series and EX9200 Series:
* All versions earlier than 20.4R3-S7;
* 21.1 versions earlier than 21.1R3-S5;
* 21.2 versions earlier than 21.2R3-S5;
* 21.3 versions earlier than 21.3R3-S4;
* 21.4 versions earlier than 21.4R3-S4;
* 22.1 versions earlier than 22.1R3-S2;
* 22.2 versions earlier than 22.2R3-S2;
* 22.3 versions earlier than 22.3R2-S2, 22.3R3;
* 22.4 versions earlier than 22.4R1-S2, 22.4R2-S2, 22.4R3.
Project Subscriptions
| Vendors | Products |
|---|---|
|
Juniper
Subscribe
|
Ex9200
Subscribe
Ex9204
Subscribe
Ex9208
Subscribe
Junos
Subscribe
Mx10
Subscribe
Mx10000
Subscribe
Mx10003
Subscribe
Mx10004
Subscribe
Mx10008
Subscribe
Mx10016
Subscribe
Mx104
Subscribe
Mx150
Subscribe
Mx2008
Subscribe
Mx2010
Subscribe
Mx2020
Subscribe
Mx204
Subscribe
Mx240
Subscribe
Mx304
Subscribe
Mx40
Subscribe
Mx480
Subscribe
Mx5
Subscribe
Mx80
Subscribe
Mx960
Subscribe
|
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2024-19255 | An Unsupported Feature in the UI vulnerability in Juniper Networks Junos OS on MX Series and EX9200 Series allows an unauthenticated, network-based attacker to cause partial impact to the integrity of the device. If the "tcp-reset" option is added to the "reject" action in an IPv6 filter which matches on "payload-protocol", packets are permitted instead of rejected. This happens because the payload-protocol match criteria is not supported in the kernel filter causing it to accept all packets without taking any other action. As a fix the payload-protocol match will be treated the same as a "next-header" match to avoid this filter bypass. This issue doesn't affect IPv4 firewall filters. This issue affects Juniper Networks Junos OS on MX Series and EX9200 Series: * All versions earlier than 20.4R3-S7; * 21.1 versions earlier than 21.1R3-S5; * 21.2 versions earlier than 21.2R3-S5; * 21.3 versions earlier than 21.3R3-S4; * 21.4 versions earlier than 21.4R3-S4; * 22.1 versions earlier than 22.1R3-S2; * 22.2 versions earlier than 22.2R3-S2; * 22.3 versions earlier than 22.3R2-S2, 22.3R3; * 22.4 versions earlier than 22.4R1-S2, 22.4R2-S2, 22.4R3. |
Solution
The following software releases have been updated to resolve this specific issue: Junos OS 20.4R3-S7, 21.1R3-S5, 21.2R3-S5, 21.3R3-S4, 21.4R3-S4, 22.1R3-S2, 22.2R3-S2, 22.3R2-S2, 22.3R3, 22.4R1-S2, 22.4R2-S2, 22.4R3, 23.2R1, and all subsequent releases.
Workaround
A workarounds is to replace the payload-protocol match with a next-header match like in the following example: [ firewall family inet6 filter <filter name> term <term name> match next-header] [ firewall family inet6 filter <filter name> term <term name> then reject tcp-reset ]
Wed, 16 Jul 2025 13:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
epss
|
epss
|
Tue, 17 Jun 2025 21:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: juniper
Published:
Updated: 2025-06-17T21:09:19.924Z
Reserved: 2023-12-27T19:38:25.708Z
Link: CVE-2024-21607
Updated: 2024-08-01T22:27:35.403Z
Status : Modified
Published: 2024-01-12T01:15:49.057
Modified: 2024-11-21T08:54:42.600
Link: CVE-2024-21607
No data.
OpenCVE Enrichment
No data.
EUVD