Protect yourself against future threats.
===========================================================================
AUSCERT External Security Bulletin Redistribution
ESB-2024.2232
2024-04 Security Bulletin: 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 (CVE-2024-30391)
11 April 2024
===========================================================================
AusCERT Security Bulletin Summary
---------------------------------
Product: Junos OS
Publisher: Juniper Networks
Operating System: Juniper
Resolution: Patch/Upgrade
CVE Names: CVE-2024-30391
Original Bulletin:
https://supportportal.juniper.net/s/article/2024-04-Security-Bulletin-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-CVE-2024-30391
Comment: CVSS (Max): 4.8 CVE-2024-30391 (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L)
CVSS Source: Juniper Networks
Calculator: https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L
- --------------------------BEGIN INCLUDED TEXT--------------------
Article ID: JSA79188
Product Affected: This issue affects all versions of Junos OS.
Severity Level: Medium
CVSS Score: CVSS 3.1
Problem:
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:
o All versions before 20.4R3-S7,
o 21.1 versions before 21.1R3,
o 21.2 versions before 21.2R2-S1, 21.2R3,
o 21.3 versions before 21.3R1-S2, 21.3R2.
For a device to be affected IPsec must be configured with either hmac-sha-384
or hmac-sha-512 as follows:
[security ipsec proposal <proposal> authentication-algorithm hmac-
sha-384/hmac-sha-512]
Solution:
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.
This issue is being tracked as 1557177 which is visible on the Customer Support
website.
Note: Juniper SIRT's policy is not to evaluate releases which are beyond End of
Engineering (EOE) or End of Life (EOL).
Workaround:
There are no known workarounds for this issue.
Modification History:
2024-04-10 - Initial Publication
Related Information:
o KB16613: Overview of the Juniper Networks SIRT Quarterly Security Bulletin
Publication Process
o KB16765: In which releases are vulnerabilities fixed?
o KB16446: Common Vulnerability Scoring System (CVSS) and Juniper's Security
Advisories
o Report a Security Vulnerability - How to Contact the Juniper Networks
Security Incident Response Team
o https://www.cve.org/CVERecord?id=CVE-2024-30391
Last Updated: 2024-04-10
Created: 2024-04-10
- --------------------------END INCLUDED TEXT----------------------
You have received this e-mail bulletin as a result of your organisation's
registration with AusCERT. The mailing list you are subscribed to is
maintained within your organisation, so if you do not wish to continue
receiving these bulletins you should contact your local IT manager. If
you do not know who that is, please send an email to auscert@auscert.org.au
and we will forward your request to the appropriate person.
NOTE: Third Party Rights
This security bulletin is provided as a service to AusCERT's members. As
AusCERT did not write the document quoted above, AusCERT has had no control
over its content. The decision to follow or act on information or advice
contained in this security bulletin is the responsibility of each user or
organisation, and should be considered in accordance with your organisation's
site policies and procedures. AusCERT takes no responsibility for consequences
which may arise from following or acting on information or advice contained in
this security bulletin.
NOTE: This is only the original release of the security bulletin. It may
not be updated when updates to the original are made. If downloading at
a later date, it is recommended that the bulletin is retrieved directly
from the author's website to ensure that the information is still current.
Contact information for the authors of the original document is included
in the Security Bulletin above. If you have any questions or need further
information, please contact them directly.
Previous advisories and external security bulletins can be retrieved from:
https://www.auscert.org.au/bulletins/
===========================================================================
Australian Computer Emergency Response Team
The University of Queensland
Brisbane
Qld 4072
Internet Email: auscert@auscert.org.au
Facsimile: (07) 3365 7031
Telephone: (07) 3365 4417 (International: +61 7 3365 4417)
AusCERT personnel answer during Queensland business hours
which are GMT+10:00 (AEST).
On call after hours for member emergencies only.
===========================================================================