7.5
CWE
20 1285
Advisory Published
Updated

CVE-2022-22201: SRX5000 Series with SPC3, SRX4000 Series, and vSRX: When PowerMode IPsec is configured, the PFE will crash upon receipt of a malformed ESP packet

First published: Tue Oct 18 2022(Updated: )

An Improper Validation of Specified Index, Position, or Offset in Input vulnerability in the Packet Forwarding Engine (PFE) of Juniper Networks Junos OS allows an unauthenticated network-based attacker to cause a Denial of Service (DoS). On SRX5000 Series with SPC3, SRX4000 Series, and vSRX, when PowerMode IPsec is configured and a malformed ESP packet matching an established IPsec tunnel is received the PFE crashes. This issue affects Juniper Networks Junos OS on SRX5000 Series with SPC3, SRX4000 Series, and vSRX: All versions prior to 19.4R2-S6, 19.4R3-S7; 20.1 versions prior to 20.1R3-S3; 20.2 versions prior to 20.2R3-S4; 20.3 versions prior to 20.3R3-S3; 20.4 versions prior to 20.4R3-S2; 21.1 versions prior to 21.1R3; 21.2 versions prior to 21.2R3; 21.3 versions prior to 21.3R1-S2, 21.3R2.

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-r3-s7
Juniper JUNOS=20.1
Juniper JUNOS=20.1-r1
Juniper JUNOS=20.1-r1-s1
Juniper JUNOS=20.1-r1-s2
Juniper JUNOS=20.1-r1-s3
Juniper JUNOS=20.1-r1-s4
Juniper JUNOS=20.1-r2
Juniper JUNOS=20.1-r2-s1
Juniper JUNOS=20.1-r2-s2
Juniper JUNOS=20.1-r3
Juniper JUNOS=20.1-r3-s1
Juniper JUNOS=20.1-r3-s2
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.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.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=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.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.3-r1
Juniper JUNOS=21.3-r1-s1
Juniper JUNOS=21.3-r2
Juniper Srx4000
Juniper Srx4100
Juniper Srx4200
Juniper Srx4600
Juniper Srx5000
Juniper Srx5400
Juniper Srx5600
Juniper Srx5800
Juniper vSRX

Remedy

The following software releases have been updated to resolve this specific issue: 19.4R2-S6, 19.4R3-S7, 20.1R3-S3, 20.2R3-S4, 20.3R3-S3, 20.4R3-S2, 21.1R3, 21.2R3, 21.3R1-S2, 21.3R2, 21.4R1, 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.

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