F5 Products: CVSS (Max): 7.5

May 9, 2024

===========================================================================
AUSCERT External Security Bulletin Redistribution

ESB-2024.2885
K000139037 : TMM vulnerability CVE-2024-25560
9 May 2024

===========================================================================

AusCERT Security Bulletin Summary
———————————

Product: BIG-IP (AFM)
BIG-IP Next CNF
Publisher: F5 Networks
Operating System: F5
Resolution: Patch/Upgrade
CVE Names: CVE-2024-3296 CVE-2024-25560

Original Bulletin:
https://my.f5.com/manage/s/article/K000139037

Comment: CVSS (Max): 7.5 CVE-2024-25560 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H)
CVSS Source: F5 Networks
Calculator: https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

– ————————–BEGIN INCLUDED TEXT——————–

K000139037: TMM vulnerability CVE-2024-25560

Published Date: May 8, 2024
AI Recommended Content

Security Advisory Description

When BIG-IP AFM is licensed and provisioned, undisclosed DNS traffic can cause
the Traffic Management Microkernel (TMM) to terminate. (CVE-2024-25560)

Impact

Traffic is disrupted while the TMM process restarts. This vulnerability allows
a remote unauthenticated attacker to cause a denial-of-service (DoS) on the
BIG-IP system or BIG-IP Next CNF instance. There is no control plane exposure;
this is a data plane issue only.

Security Advisory Status

F5 Product Development has assigned ID 1317705 (BIG-IP and BIG-IP Next CNF) to
this vulnerability. This issue has been classified as CWE-476: NULL Pointer
Dereference.

To determine if your product and version have been evaluated for this
vulnerability, refer to the Evaluated products box. To determine if your
release is known to be vulnerable, the components or features that are affected
by the vulnerability, and for information about releases, point releases, or
hotfixes that address the vulnerability, refer to the following tables. You can
also use iHealth to diagnose a vulnerability for BIG-IP and BIG-IQ systems. For
more information about using iHealth, refer to K27404821: Using F5 iHealth to
diagnose vulnerabilities. For more information about security advisory
versioning, refer to K51812227: Understanding security advisory versioning.

In this section

o BIG-IP Next
o BIG-IP and BIG-IQ
o F5 Distributed Cloud Services
o F5OS
o NGINX
o Other products

BIG-IP Next

Note: After a fix is introduced for a given minor branch, that fix applies to
all subsequent maintenance and point releases for that branch, and no
additional fixes for that branch will be listed in the table. For example, when
a fix is introduced in 20.0.2, the fix also applies to 20.0.3, and all later
20.1.x releases. For more information, refer to K51812227: Understanding
security advisory versioning.

+———&# | | |Product |Branch|to be | | +———&# |BIG-IP Next| | |(all |All |None |modules) | | +———&# |BIG-IP Next| | |Central |All |None |Manager | | +———&# |BIG-IP Next| | |SPK |All |None | | | +———&# |BIG-IP Next|1.x |CNF | | +———&# 8211;+——+————–+———-+———–+——+————-+
|Versions known|Fixes | |CVSSv3|Vulnerable |
|introduced|Severity |score^|component or |
|vulnerable^1 |in | |2 |feature |
8211;+——+————–+———-+———–+——+————-+
|Not |Not | | |
|applicable|vulnerable^|None |None |
| |3 | | |
8211;+——+————–+———-+———–+——+————-+
|Not |Not | | |
|applicable|vulnerable |None |None |
| | | | |
8211;+——+————–+———-+———–+——+————-+
|Not |Not | | |
|applicable|vulnerable^|None |None |
| |3 | | |
8211;+——+————–+———-+———–+——+————-+
|1.1.0 – 1.1.1 |1.2.0 |High |7.5 |TMM |
| | | | |
8211;+——+————–+———-+———–+——+————-+

^1F5 evaluates only software versions that have not yet reached the End of
Technical Support (EoTS) phase of their lifecycle. For more information, refer
to the Security hotfixes section of K4602: Overview of the F5 security
vulnerability response policy.

^2The CVSSv3 score link takes you to a resource outside of MyF5, and the
content may be removed without our knowledge.

^3The specified products contain the affected code. However, F5 identifies the
vulnerability status as Not vulnerable because the attacker cannot exploit the
code in default, standard, or recommended configurations.

BIG-IP and BIG-IQ

Note: After a fix is introduced for a given minor branch, that fix applies to
all subsequent maintenance and point releases for that branch, and no
additional fixes for that branch will be listed in the table. For example, when
a fix is introduced in 16.1.2.1, the fix also applies to 16.1.2.2, and all
later 16.1.x releases (16.1.3.x, 16.1.4.x). For more information, refer to
K51812227: Understanding security advisory versioning.

+————+——+————–+———-+———-+——+————-+
| | |Versions known|Fixes | |CVSSv3|Vulnerable |
|Product |Branch|to be |introduced|Severity |score^|component or |
| | |vulnerable^1 |in | |2 |feature |
+————+——+————–+———-+———-+——+————-+
| |17.x |17.1.0 |17.1.1 | | | |
| +——+————–+———-+ | | |
| |16.x |16.1.0 – |16.1.4 | | | |
|BIG-IP (AFM)| |16.1.3 | |High |7.5 |TMM |
| +——+————–+———-+ | | |
| |15.x |15.1.0 – |None | | | |
| | |15.1.10 | | | | |
+————+——+————–+———-+———-+——+————-+
|BIG-IP (all | | |Not |Not | | |
|other |All |None |applicable|vulnerable|None |None |
|modules) | | | | | | |
+————+——+————–+———-+———-+——+————-+
|BIG-IQ | | |Not |Not | | |
|Centralized |All |None |applicable|vulnerable|None |None |
|Management | | | | | | |
+————+——+————–+———-+———-+——+————-+

^2The CVSSv3 score link takes you to a resource outside of MyF5, and the
content may be removed without our knowledge.

F5 Distributed Cloud Services

F5OS

NGINX

Other products

Security Advisory Recommended Actions

If you are running a version listed in the Versions known to be vulnerable
column, you can eliminate this vulnerability by installing a version listed in
the Fixes introduced in column. If the Fixes introduced in column does not list
a version for your branch, then no update candidate currently exists for that
branch and F5 recommends that you upgrade to a version with the fix (refer to
the tables).

If the Fixes introduced in column lists a version prior to the one you are
running, in the same branch, then your version should have the fix.

Mitigation

F5 recommends you configure the BIG-IP systems with high availability (HA) to
lessen the impact of the vulnerability.

o Configure systems with HA clustering. For more information, refer to
K02234544: Manually setting up device service clustering.
o Configure the HA table to take specific actions. For more information,
refer to K9231: Overview of BIG-IP daemon heartbeat failsafe.

Acknowledgments

This issue was discovered internally by F5.

Related Content

o K41942608: Overview of MyF5 security advisory articles
o K12201527: Overview of Quarterly Security Notifications
o K51812227: Understanding security advisory versioning
o K4602: Overview of the F5 security vulnerability response policy
o K4918: Overview of the F5 critical issue hotfix policy
o K39757430: F5 product and services lifecycle policy index
o K9502: BIG-IP hotfix and point release matrix
o K13123: Managing BIG-IP product hotfixes (11.x – 17.x)
o K000090258: Download F5 products from MyF5
o K9970: Subscribing to email notifications regarding F5 products
o K9957: Creating a custom RSS feed to view new and updated documents
o K44525501: Overview of BIG-IP data plane and control plane
o K000135931: Contact F5 Support

AI Recommended Content

o K10866411 : Creating a custom cipher group using the Configuration utility
o K5903 : BIG-IP software support policy
o K000139508 : rust-openssl vulnerability CVE-2024-3296
o K000135931 : Contact F5 Support

Return to Top

– ————————–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.
===========================================================================Security BulletinsRead More