CVE-2024-30391: Junos OS: MX Series with SPC3, and SRX Series: When IPsec authentication is configured with "hmac-sha-384" and "hmac-sha-512" no authentication of traffic is performed

Published Apr 12, 2024
·
Updated

A Missing Authentication for Critical Function vulnerability in the Packet Forwarding Engine (pfe) of Juniper Networks Junos OS on MX Series with SPC3, and SRX Series allows an unauthenticated network-based attacker to cause limited impact to the integrity or availability of the device.

If a device is configured with IPsec authentication algorithm hmac-sha-384 or hmac-sha-512, tunnels are established normally but for traffic traversing the tunnel no authentication information is sent with the encrypted data on egress, and no authentication information is expected on ingress. So if the peer is an unaffected device transit traffic is going to fail in both directions. If the peer is an also affected device transit traffic works, but without authentication, and configuration and CLI operational commands indicate authentication is performed. This issue affects Junos OS:

All versions before 20.4R3-S7, 21.1 versions before 21.1R3,  21.2 versions before 21.2R2-S1, 21.2R3,  21.3 versions before 21.3R1-S2, 21.3R2.

Affected Software

66 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.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
Juniper Junos=21.3-r1
Juniper Junos=21.3-r1-s1
Any of the following
Juniper cSRX
Juniper MX240
Juniper MX480
Juniper MX960
Juniper SRX100
Juniper SRX110
Juniper SRX1400
Juniper SRX1500
Juniper SRX1600
Juniper SRX210
Juniper SRX220
Juniper SRX2300
Juniper SRX240
Juniper Srx240h2
Juniper SRX240m
Juniper SRX300
Juniper SRX320
Juniper SRX340
Juniper SRX3400
Juniper SRX345
Juniper SRX3600
Juniper Srx380
Juniper SRX4000
Juniper SRX4100
Juniper SRX4200
Juniper SRX4300
Juniper SRX4600
Juniper SRX4700
Juniper SRX5000
Juniper SRX5400
Juniper SRX550
Juniper Srx550 Hm
Juniper SRX550m
Juniper SRX5600
Juniper SRX5800
Juniper SRX650
Juniper vSRX
Juniper Networks Junos OS<20.4R3-S7, <21.1R3, <21.2R2-S1, >=21.2R3<21.2R3, <21.3R1-S2, <21.3R2

Remediation

Information

The following software releases have been updated to resolve this specific issue: 20.4R3-S7, 21.1R3, 21.2R2-S1, 21.2R3, 21.3R1-S2, 21.3R2, 21.4R1, and all subsequent releases. Please note that for releases earlier than 21.1 the affected CLI options have been removed. For releases from 21.1 onwards the issue has been fixed.

Event History

Apr 12, 2024
CVE Published
via MITRE·03:25 PM
Data Sourced
via MITRE·03:25 PM
RemedyDescriptionSeverityWeakness
Data Sourced
via NVD·04:15 PM
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-30391?

CVE-2024-30391 has a limited impact on the integrity and availability of the affected devices.

2

How do I fix CVE-2024-30391?

To remediate CVE-2024-30391, update your Junos OS to a version that is not affected, specifically above 21.3R2.

3

What products are impacted by CVE-2024-30391?

CVE-2024-30391 affects Juniper Networks Junos OS on MX Series with SPC3 and SRX Series devices.

4

Can CVE-2024-30391 be exploited remotely?

Yes, CVE-2024-30391 can be exploited by an unauthenticated network-based attacker.

5

What type of vulnerability is CVE-2024-30391?

CVE-2024-30391 is classified as a Missing Authentication for Critical Function vulnerability.

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