ESB-2023.3883 – [Appliance] F5 Products: CVSS (Max): 5.9 [auscert.org.au]

—–BEGIN PGP SIGNED MESSAGE—–
Hash: SHA256

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

ESB-2023.3883
K000135178 : OpenSSL vulnerability CVE-2023-2650
12 July 2023

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

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

Product: BIG-IP (all modules)
BIG-IQ
F5OS-A
F5OS-C
Traffix SDC
Publisher: F5 Networks
Operating System: Network Appliance
Resolution: Mitigation
CVE Names: CVE-2023-2650

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

Comment: CVSS (Max): 5.9 CVE-2023-2650 (CVSS:3.1/AV:N/AC:H/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:H/PR:N/UI:N/S:U/C:N/I:N/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——————–

K000135178: OpenSSL vulnerability CVE-2023-2650

Published Date: Jun 22, 2023

Security Advisory Description

Issue summary: Processing some specially crafted ASN.1 object identifiers or
data containing them may be very slow. Impact summary: Applications that use
OBJ_obj2txt() directly, or use any of the OpenSSL subsystems OCSP, PKCS7/SMIME,
CMS, CMP/CRMF or TS with no message size limit may experience notable to very
long delays when processing those messages, which may lead to a Denial of
Service. An OBJECT IDENTIFIER is composed of a series of numbers –
sub-identifiers – most of which have no size limit. OBJ_obj2txt() may be used
to translate an ASN.1 OBJECT IDENTIFIER given in DER encoding form (using the
OpenSSL type ASN1_OBJECT) to its canonical numeric text form, which are the
sub-identifiers of the OBJECT IDENTIFIER in decimal form, separated by periods.
When one of the sub-identifiers in the OBJECT IDENTIFIER is very large (these
are sizes that are seen as absurdly large, taking up tens or hundreds of KiBs),
the translation to a decimal number in text may take a very long time. The time
complexity is O(n^2) with ‘n’ being the size of the sub-identifiers in bytes
(*). With OpenSSL 3.0, support to fetch cryptographic algorithms using names /
identifiers in string form was introduced. This includes using OBJECT
IDENTIFIERs in canonical numeric text form as identifiers for fetching
algorithms. Such OBJECT IDENTIFIERs may be received through the ASN.1 structure
AlgorithmIdentifier, which is commonly used in multiple protocols to specify
what cryptographic algorithm should be used to sign or verify, encrypt or
decrypt, or digest passed data. Applications that call OBJ_obj2txt() directly
with untrusted data are affected, with any version of OpenSSL. If the use is
for the mere purpose of display, the severity is considered low. In OpenSSL 3.0
and newer, this affects the subsystems OCSP, PKCS7/SMIME, CMS, CMP/CRMF or TS.
It also impacts anything that processes X.509 certificates, including simple
things like verifying its signature. The impact on TLS is relatively low,
because all versions of OpenSSL have a 100KiB limit on the peer’s certificate
chain. Additionally, this only impacts clients, or servers that have explicitly
enabled client authentication. In OpenSSL 1.1.1 and 1.0.2, this only affects
displaying diverse objects, such as X.509 certificates. This is assumed to not
happen in such a way that it would cause a Denial of Service, so these versions
are considered not affected by this issue in such a way that it would be cause
for concern, and the severity is therefore considered low. (CVE-2023-2650)

Impact

For BIG-IP systems, Transport Layer Security (TLS) is impacted when client
authentication is enabled in the control plane (httpd) or data plane (SSL
profiles). The impact on TLS is relatively low because all versions of OpenSSL
have a 100 KiB limit on the peer’s certificate chain. Additionally, any
applications that use OBJ_obj2txt() directly or use any of the OpenSSL
subsystems OCSP, PKCS7/SMIME, CMS, CMP/CRMF or TS with no message size limit
may experience notable to very long delays when processing those messages,
which may lead to a denial-of-service (DoS).

Security Advisory Status

F5 Product Development has assigned ID 1304081 (BIG-IP), ID 1304081-1 (BIG-IQ),
ID 1304537 (F5OS), and SDC-2306 and SDC-2305 (Traffix SDC) 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 |Fixes | |CVSSv3|Vulnerable |
|Product |Branch|known to be |introduced|Severity |score^|component or |
| | |vulnerable^1 |in | |2 |feature |
+———–+——+————-+———-+———-+——+—————+
| |17.x |17.0.0 – |None | | | |
| | |17.1.0 | | | | |
| +——+————-+———-+ | | |
| |16.x |16.1.0 – |None | | |Control plane: |
| | |16.1.3 | | | |httpd/OpenSSL |
| +——+————-+———-+ | | |
|BIG-IP (all|15.x |15.1.0 – |None |Low |3.7 |Data plane: |
|modules) | |15.1.9 | | | |TMM (Client SSL|
| +——+————-+———-+ | |and Server SSL |
| |14.x |14.1.0 – |None | | |profiles) |
| | |14.1.5 | | | | |
| +——+————-+———-+ | | |
| |13.x |13.1.0 – |None | | | |
| | |13.1.5 | | | | |
+———–+——+————-+———-+———-+——+—————+
|BIG-IP Next|All |None |Not |Not |None |None |
|SPK | | |applicable|vulnerable| | |
+———–+——+————-+———-+———-+——+—————+
|BIG-IQ | | | | | | |
|Centralized|8.x |8.0.0 – 8.3.0|None |Low |3.7 |httpd/OpenSSL |
|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

^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

Other products

^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

To mitigate this vulnerability, refer to the following sections:

o Data plane (BIG-IP)
o Control plane (BIG-IP and BIG-IQ)

Data plane (BIG-IP)

o Do not configure client certificate authentication for the Client SSL
profile or server certificate authentication for the Server SSL profile.
? For information about Client Authentication settings in the Client SSL
profile, refer to K14783: Overview of the Client SSL profile (11.x –
17.x).
? For information about Server Authentication settings in the Server SSL
profile, refer to K14806: Overview of the Server SSL profile (11.x –
17.x).

Control plane (BIG-IP and BIG-IQ)

o Do not configure httpd for client-side certificate authentication in the
server as described in K12042624: Restricting access to the Configuration
utility using client certificates (13.x – 16.x). If client-side
certificates have been previously implemented, remove them.

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 K15106: Managing BIG-IQ product hotfixes
o K15113: BIG-IQ hotfix and point release matrix
o K48955220: Installing an OPSWAT Endpoint Security update on BIG-IP APM
systems (11.4.x and later)
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
o K44525501: Overview of BIG-IP data plane and control plane

– ————————–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/

iQIVAwUBZK4RdMkNZI30y1K9AQiB4g/+NUuAyS2MlfG86c3W5ogVS/J3DqZM6cnA
HL0nn/JUoZo98ZVyA5vSkVKz/KJ48Hn9+ulgERbdt15GjyAEkeCDoOKFQoAoxzeo
t+PXPsm0CkZEOqjnI04yV6TrPMazEUZswF2mzGZp6hAT0IyJs4pASPchEb9k6y5r
q19FVD/ZUAL+u/b9SK2htCaNTGEGTjsiesDhLgqW87k0IWACl4NofwUJ+qZb1nGC
DdYQjIzyEejAc6ynR4r4GRnR8qgQeCPkp/lhPJdBbM6VNNLFvBo0nW1MJ3MA897G
Ry8P8IJu4VJbg2PA8pj7/7e/v4Hh2oSnDp7m0SsvNDCNDn4VVPGSThParcVV1iI+
6u3MYDEGFHiZPqoqzJpMFZojCYuzt24n6kZ22BHpveC0lqhjzzerKjOmDtFe48lN
yhiEROvQa+nyQC5MiN9k8tX45BRY9+BmP5cpzscsHgyZYotSoy2EKLN6ZlzqdkyV
mwjbiY7mCOwqH9UPpoSW3WTjMUeC+HWp/WvuSFLeTPHblAyw3YjXmu55FCykk4rG
1xn1uEtjSok0JQdAWMigoOJ0kuZESg9DZCtHOgrYJwyPk2uXKQZ5wtcljP99vTiz
fSSQFHNu/XX3EeGq2f4oCoYYH/dLlwyw5Ll9wn1gjpSP/i8zn7xklQ4WtM00k4eo
oHuMA8co8xw=
=NYwn
—–END PGP SIGNATURE—–

Source: Read More

Security Bulletins

Leave a Comment Cancel reply