ESB-2023.3882 – [Appliance] Traffix SDC: CVSS (Max): 7.8 [auscert.org.au]

—–BEGIN PGP SIGNED MESSAGE—–
Hash: SHA256

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

ESB-2023.3882
K000135122 : Linux kernel vulnerability CVE-2023-0461
12 July 2023

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

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

Product: Traffix SDC
Publisher: F5 Networks
Operating System: Network Appliance
Resolution: Mitigation
CVE Names: CVE-2023-0461

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

Comment: CVSS (Max): 7.8 CVE-2023-0461 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H)
CVSS Source: NVD
Calculator: https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

**AusCERT wishes to advise that there has been a delay in reporting F5 security notifications for
June, 2023 due to a technical issue which has been identified. This issue has been rectified.

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

K000135122: Linux kernel vulnerability CVE-2023-0461

Published Date: Jun 20, 2023

Security Advisory Description

There is a use-after-free vulnerability in the Linux Kernel which can be
exploited to achieve local privilege escalation. To reach the vulnerability
kernel configuration flag CONFIG_TLS or CONFIG_XFRM_ESPINTCP has to be
configured, but the operation does not require any privilege. There is a
use-after-free bug of icsk_ulp_data of a struct inet_connection_sock. When
CONFIG_TLS is enabled, user can install a tls context (struct tls_context) on a
connected tcp socket. The context is not cleared if this socket is disconnected
and reused as a listener. If a new socket is created from the listener, the
context is inherited and vulnerable. The setsockopt TCP_ULP operation does not
require any privilege. We recommend upgrading past commit
2c02d41d71f90a5168391b6a5f2954112ba2307c (CVE-2023-0461)

Impact

A local authenticated user may be able to exploit the vulnerability to escalate
privileges and gain access to restricted information, make unauthorized
modifications to files, or cause a denial-of-service (DoS).

Security Advisory Status

F5 Product Development has assigned SDC-2323 (Traffix) to this vulnerability.

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 and BIG-IQ
o F5OS
o NGINX
o Other products

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 14.1.2.3, the fix also applies to 14.1.2.4 and all later
14.1.x releases (14.1.3.x., 14.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 |
+————+——+————–+———-+———-+——+————-+
|BIG-IP (all | | |Not |Not | | |
|modules) |All |None |applicable|vulnerable|None |None |
| | | | | | | |
+————+——+————–+———-+———-+——+————-+
|BIG-IP Next |All |None |Not |Not |None |None |
|SPK | | |applicable|vulnerable| | |
+————+——+————–+———-+———-+——+————-+
|BIG-IQ | | |Not |Not | | |
|Centralized |All |None |applicable|vulnerable|None |None |
|Management | | | | | | |
+————+——+————–+———-+———-+——+————-+

^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 it is
possible that the document may be removed without our knowledge.

F5OS

+——-+——+—————-+———-+———-+——-+—————+
| | |Versions known |Fixes | |CVSSv3 |Vulnerable |
|Product|Branch|to be vulnerable|introduced|Severity |score^2|component or |
| | |^1 |in | | |feature |
+——-+——+—————-+———-+———-+——-+—————+
|F5OS-A |All |None |Not |Not |None |None |
| | | |applicable|vulnerable| | |
+——-+——+—————-+———-+———-+——-+—————+
|F5OS-C |All |None |Not |Not |None |None |
| | | |applicable|vulnerable| | |
+——-+——+—————-+———-+———-+——-+—————+

^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 it is
possible that the document may be removed without our knowledge.

NGINX

+———+——+—————+———-+———-+——+—————+
| | |Versions known |Fixes | |CVSSv3|Vulnerable |
|Product |Branch|to be |introduced|Severity |score^|component or |
| | |vulnerable^1 |in | |2 |feature |
+———+——+—————+———-+———-+——+—————+
|NGINX | | |Not |Not | | |
|(all |All |None |applicable|vulnerable|None |None |
|products)| | | | | | |
+———+——+—————+———-+———-+——+—————+

^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 it is
possible that the document may be removed without our knowledge.

Other products

+——-+——+—————–+———-+——–+——-+—————-+
| | |Versions known to|Fixes | |CVSSv3 |Vulnerable |
|Product|Branch|be vulnerable^1 |introduced|Severity|score^2|component or |
| | | |in | | |feature |
+——-+——+—————–+———-+——–+——-+—————-+
|Traffix|5.x |5.2.0 |None |High |7.8 |Linux kernel |
|SDC | | | | | | |
+——-+——+—————–+———-+——–+——-+—————-+

^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 it is
possible that the document may be removed without our knowledge.

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

Limit access to the Traffix management command line interface to trusted users.

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 K167: Downloading software and firmware from F5
o K9970: Subscribing to email notifications regarding F5 products
o K9957: Creating a custom RSS feed to view new and updated documents

– ————————–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 [email protected]
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: [email protected]
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.
===========================================================================
—–BEGIN PGP SIGNATURE—–
Comment: https://auscert.org.au/gpg-key/

iQIVAwUBZK4REckNZI30y1K9AQiISg//d8Hfay0bzLcd9dxRvMdwiRDx6shBnnjL
YyJQRSLzUTopsoPOifixPrjRwAkId5XjiPMULOvL2X4swAOZbhrxg/bOY8npxesm
iYv0xp6k4IeMQFeZk3pbQAss0+DQhLt3FqYwmmjGOxqeplliJBemvJmDT5aLmy4I
u+ome7izd962vDlQymb41+rSUebkYx62oQLEnzrkHdHt2oIqknqtWhZ9/9BhvUi4
Equ6E3Js7xxPqGZi8wylN12DScArXnTmua3IoJhf1XS6m7+0q3ABWKu82VU/f80p
kbgnjt+C5D60lZ6iU8OsrWkTQ2lNPJtmA0aLPF1CJ7d0m1ZLsiMSJy1nR8Rs3Kse
zHyJ+Hv1j45H2kSdTD9RHdADZxJFbtdxuvvLQFh27MgZogG2ehPog0O/ad9srMzl
YSR3DFXr1rcnalmwt7ChoFnSYEYWJfdSKP73Q2siJfrCPIQonPMKVAjfI66LLWui
jmaOWDiaTioRRRRx40ftRhyXgg4UiqtON/9h8ikPSjUXnaZT+vfIp89YiBvlr1eb
OP4x5RiKAwg8EE7OzYxkOwakruUTEL1TQQ+GKfXxJPS/wipaJ1ln+PK4IOLI6y/k
YJA4RXm4eHthdsQVMlYozLBV4eUqPHq6+iLqDx6xXgjD7Jalcooqu4gBoA+uiGR0
i4E+ojdKLWA=
=kYGp
—–END PGP SIGNATURE—–

Source: Read More

​

Security Bulletins

Leave a Comment