7.5
CWE
703
Advisory Published
Updated

CVE-2023-22413: Junos OS: MX Series: The Multiservices PIC Management Daemon (mspmand) will crash when an IPsec6 tunnel processes specific IPv4 packets

First published: Thu Jan 12 2023(Updated: )

An Improper Check or Handling of Exceptional Conditions vulnerability in the IPsec library of Juniper Networks Junos OS allows a network-based, unauthenticated attacker to cause Denial of Service (DoS). On all MX platforms with MS-MPC or MS-MIC card, when specific IPv4 packets are processed by an IPsec6 tunnel, the Multiservices PIC Management Daemon (mspmand) process will core and restart. This will lead to FPC crash. Traffic flow is impacted while mspmand restarts. Continued receipt of these specific packets will cause a sustained Denial of Service (DoS) condition. This issue only occurs if an IPv4 address is not configured on the multiservice interface. This issue affects: Juniper Networks Junos OS on MX Series All versions prior to 19.4R3-S9; 20.1 version 20.1R3-S5 and later versions; 20.2 versions prior to 20.2R3-S5; 20.3 versions prior to 20.3R3-S5; 20.4 versions prior to 20.4R3-S4; 21.1 versions prior to 21.1R3-S3; 21.2 versions prior to 21.2R3-S1; 21.3 versions prior to 21.3R3; 21.4 versions prior to 21.4R2-S1, 21.4R3; 22.1 versions prior to 22.1R2.

Credit: sirt@juniper.net

Affected SoftwareAffected VersionHow to fix
Juniper JUNOS<19.4
Juniper JUNOS=19.4
Juniper JUNOS=19.4-r1
Juniper JUNOS=19.4-r1-s1
Juniper JUNOS=19.4-r1-s2
Juniper JUNOS=19.4-r1-s3
Juniper JUNOS=19.4-r1-s4
Juniper JUNOS=19.4-r2
Juniper JUNOS=19.4-r2-s1
Juniper JUNOS=19.4-r2-s2
Juniper JUNOS=19.4-r2-s3
Juniper JUNOS=19.4-r2-s4
Juniper JUNOS=19.4-r2-s5
Juniper JUNOS=19.4-r2-s6
Juniper JUNOS=19.4-r2-s7
Juniper JUNOS=19.4-r3
Juniper JUNOS=19.4-r3-s1
Juniper JUNOS=19.4-r3-s2
Juniper JUNOS=19.4-r3-s3
Juniper JUNOS=19.4-r3-s4
Juniper JUNOS=19.4-r3-s5
Juniper JUNOS=19.4-r3-s6
Juniper JUNOS=19.4-r3-s7
Juniper JUNOS=19.4-r3-s8
Juniper JUNOS=20.1-r3-s5
Juniper JUNOS=20.2
Juniper JUNOS=20.2-r1
Juniper JUNOS=20.2-r1-s1
Juniper JUNOS=20.2-r1-s2
Juniper JUNOS=20.2-r1-s3
Juniper JUNOS=20.2-r2
Juniper JUNOS=20.2-r2-s1
Juniper JUNOS=20.2-r2-s2
Juniper JUNOS=20.2-r2-s3
Juniper JUNOS=20.2-r3
Juniper JUNOS=20.2-r3-s1
Juniper JUNOS=20.2-r3-s2
Juniper JUNOS=20.2-r3-s3
Juniper JUNOS=20.2-r3-s4
Juniper JUNOS=20.3
Juniper JUNOS=20.3-r1
Juniper JUNOS=20.3-r1-s1
Juniper JUNOS=20.3-r1-s2
Juniper JUNOS=20.3-r2
Juniper JUNOS=20.3-r2-s1
Juniper JUNOS=20.3-r3
Juniper JUNOS=20.3-r3-s1
Juniper JUNOS=20.3-r3-s2
Juniper JUNOS=20.3-r3-s3
Juniper JUNOS=20.3-r3-s4
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=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.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.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.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=22.1-r1
Juniper JUNOS=22.1-r1-s1
Juniper JUNOS=22.1-r1-s2
Juniper Mx10
Juniper Mx10000
Juniper Mx10003
Juniper Mx10008
Juniper Mx10016
Juniper Mx104
Juniper Mx150
Juniper Mx2008
Juniper Mx2010
Juniper Mx2020
Juniper Mx204
Juniper Mx240
Juniper Mx40
Juniper Mx480
Juniper Mx5
Juniper Mx80
Juniper Mx960

Remedy

The following software releases have been updated to resolve this specific issue: 19.4R3-S9, 20.2R3-S5, 20.3R3-S5, 20.4R3-S4, 21.1R3-S3, 21.2R3-S1, 21.3R3, 21.4R3, 22.1R2, 22.2R1, and all subsequent releases.

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Frequently Asked Questions

  • What is the severity of CVE-2023-22413?

    CVE-2023-22413 is classified as a high severity vulnerability due to its potential to cause Denial of Service (DoS) in affected systems.

  • How do I fix CVE-2023-22413?

    To remediate CVE-2023-22413, update your Junos OS to a version that addresses this vulnerability as recommended by Juniper Networks.

  • Which devices are affected by CVE-2023-22413?

    CVE-2023-22413 affects all MX platforms with MS-MPC or MS-MIC cards running vulnerable versions of Junos OS.

  • What type of attack can exploit CVE-2023-22413?

    CVE-2023-22413 can be exploited by a network-based, unauthenticated attacker to trigger Denial of Service conditions.

  • What versions of Junos OS are vulnerable to CVE-2023-22413?

    Versions of Junos OS prior to 19.4 and on specific 19.4 releases are vulnerable to CVE-2023-22413.

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.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203