CVE-2024-21607: Junos OS: MX Series and EX9200 Series: If the "tcp-reset" option used in an IPv6 filter, matched packets are accepted instead of rejected

Published Jan 12, 2024
·
Updated

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.

Affected Software

110 affected components
All of the following
Any of the following
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=21.1
Juniper Junos=21.1-r1
Juniper Junos=21.1-r1-s1
Juniper Junos=21.1-r2
Juniper Junos=21.1-r2-s1
Juniper Junos=21.1-r2-s2
Juniper Junos=21.1-r3
Juniper Junos=21.1-r3-s1
Juniper Junos=21.1-r3-s2
Juniper Junos=21.1-r3-s3
Juniper Junos=21.1-r3-s4
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.3
Juniper Junos=21.3-r1
Juniper Junos=21.3-r1-s1
Juniper Junos=21.3-r1-s2
Juniper Junos=21.3-r2
Juniper Junos=21.3-r2-s1
Juniper Junos=21.3-r2-s2
Juniper Junos=21.3-r3
Juniper Junos=21.3-r3-s1
Juniper Junos=21.3-r3-s2
Juniper Junos=21.3-r3-s3
Juniper Junos=21.4
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=22.1
Juniper Junos=22.1-r1
Juniper Junos=22.1-r1-s1
Juniper Junos=22.1-r1-s2
Juniper Junos=22.1-r2
Juniper Junos=22.1-r2-s1
Juniper Junos=22.1-r2-s2
Juniper Junos=22.1-r3
Juniper Junos=22.1-r3-s1
Juniper Junos=22.2
Juniper Junos=22.2-r1
Juniper Junos=22.2-r1-s1
Juniper Junos=22.2-r1-s2
Juniper Junos=22.2-r2
Juniper Junos=22.2-r2-s1
Juniper Junos=22.2-r2-s2
Juniper Junos=22.2-r3
Juniper Junos=22.2-r3-s1
Juniper Junos=22.3
Juniper Junos=22.3-r1
Juniper Junos=22.3-r1-s1
Juniper Junos=22.3-r1-s2
Juniper Junos=22.3-r2
Juniper Junos=22.3-r2-s1
Juniper Junos=22.4
Juniper Junos=22.4-r1
Juniper Junos=22.4-r1-s1
Juniper Junos=22.4-r2
Juniper Junos=22.4-r2-s1
Any of the following
Juniper EX9200
Juniper Ex9204
Juniper Ex9208
Juniper MX10
Juniper Mx10000
Juniper MX10003
Juniper Mx10004
Juniper MX10008
Juniper MX10016
Juniper MX104
Juniper MX150
Juniper MX2008
Juniper MX2010
Juniper MX2020
Juniper MX204
Juniper MX240
Juniper MX304
Juniper Mx40
Juniper MX480
Juniper Mx5
Juniper Mx80
Juniper MX960

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Juniper Networks Junos OS (MX Series and EX9200 Series) to a version that resolves this vulnerability.

    Fixed in 20.4R3-S7
  2. Upgrade

    Upgrade Juniper Networks Junos OS (MX Series and EX9200 Series) to a version that resolves this vulnerability.

    Fixed in 21.1R3-S5
  3. Upgrade

    Upgrade Juniper Networks Junos OS (MX Series and EX9200 Series) to a version that resolves this vulnerability.

    Fixed in 21.2R3-S5
  4. Upgrade

    Upgrade Juniper Networks Junos OS (MX Series and EX9200 Series) to a version that resolves this vulnerability.

    Fixed in 21.3R3-S4
  5. Upgrade

    Upgrade Juniper Networks Junos OS (MX Series and EX9200 Series) to a version that resolves this vulnerability.

    Fixed in 21.4R3-S4
  6. Upgrade

    Upgrade Juniper Networks Junos OS (MX Series and EX9200 Series) to a version that resolves this vulnerability.

    Fixed in 22.1R3-S2
  7. Upgrade

    Upgrade Juniper Networks Junos OS (MX Series and EX9200 Series) to a version that resolves this vulnerability.

    Fixed in 22.2R3-S2
  8. Upgrade

    Upgrade Juniper Networks Junos OS (MX Series and EX9200 Series) to a version that resolves this vulnerability.

    Fixed in 22.3R2-S2
  9. Upgrade

    Upgrade Juniper Networks Junos OS (MX Series and EX9200 Series) to a version that resolves this vulnerability.

    Fixed in 22.3R3
  10. Upgrade

    Upgrade Juniper Networks Junos OS (MX Series and EX9200 Series) to a version that resolves this vulnerability.

    Fixed in 22.4R1-S2
  11. Upgrade

    Upgrade Juniper Networks Junos OS (MX Series and EX9200 Series) to a version that resolves this vulnerability.

    Fixed in 22.4R2-S2
  12. Upgrade

    Upgrade Juniper Networks Junos OS (MX Series and EX9200 Series) to a version that resolves this vulnerability.

    Fixed in 22.4R3
  13. Upgrade

    Upgrade Juniper Networks Junos OS (MX Series and EX9200 Series) to a version that resolves this vulnerability.

    Fixed in 23.2R1
  14. Configuration

    On MX Series and EX9200 Series, apply the Junos OS fix so the "payload-protocol" match is handled the same as a "next-header" match to avoid filter bypass.

    Juniper Networks Junos OS IPv6 firewall filters payload-protocol match handling = Treat payload-protocol match the same as a "next-header" match
  15. Configuration

    If you have an IPv6 filter that matches on "payload-protocol", ensure the "tcp-reset" option is NOT added to the "reject" action; otherwise matched packets are permitted instead of rejected.

    Juniper Networks Junos OS IPv6 firewall filters tcp-reset option in reject action for payload-protocol match = Do not add tcp-reset to the reject action when using an IPv6 filter that matches on payload-protocol
  16. Compensating control

    Use IPv4 firewall filters for filtering where applicable, since this issue does not affect IPv4 firewall filters (payload-protocol match problem is described for IPv6 filters).

Event History

Jan 12, 2024
CVE Published
via MITRE·12:55 AM
Data Sourced
via MITRE·12:55 AM
RemedyDescriptionSeverityWeakness
Data Sourced
via NVD·01:15 AM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2024-21607?

CVE-2024-21607 has a severity rating according to the CVSS v4.0 standards.

2

How do I fix CVE-2024-21607?

To fix CVE-2024-21607, update your Junos OS to a patched version as recommended by Juniper Networks.

3

Which versions of Junos OS are affected by CVE-2024-21607?

CVE-2024-21607 affects multiple versions of Junos OS including versions below 20.4 and specific releases of 20.4 up to 22.4.

4

Can CVE-2024-21607 be exploited remotely?

Yes, CVE-2024-21607 can be exploited by unauthenticated, network-based attackers.

5

What impact does CVE-2024-21607 have on the device?

CVE-2024-21607 may cause partial impact to the integrity of the affected device.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203