—–BEGIN PGP SIGNED MESSAGE—–
Hash: SHA256
===========================================================================
AUSCERT External Security Bulletin Redistribution
ESB-2023.3881
K000134942 : Intel CPU vulnerability CVE-2022-33972
12 July 2023
===========================================================================
AusCERT Security Bulletin Summary
———————————
Product: F5OS-A
Publisher: F5 Networks
Operating System: Network Appliance
Resolution: Patch/Upgrade
CVE Names: CVE-2022-33972
Original Bulletin:
https://my.f5.com/manage/s/article/K000134942
Comment: CVSS (Max): 4.7 CVE-2022-33972 (CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:L/A:N)
CVSS Source: F5 Networks
Calculator: https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:L/A:N
**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——————–
K000134942: Intel CPU vulnerability CVE-2022-33972
Published Date: Jun 22, 2023
Security Advisory Description
Incorrect calculation in microcode keying mechanism for some 3rd Generation
Intel(R) Xeon(R) Scalable Processors may allow a privileged user to potentially
enable information disclosure via local access. (CVE-2022-33972)
Impact
This vulnerability may allow a privileged user to enable information disclosure
through local access.
The following rSeries platforms are vulnerable if their BIOS version is prior
to 2.01.134.1:
o All variants of r5600/r5800/r5900 (C129)
o All variants of r10600/r10800/r10900 (C128)
To determine the BIOS version of your F5 rSeries system, refer to K000134940:
Determine the BIOS version for an F5 rSeries hardware product.
Security Advisory Status
F5 Product Development has assigned ID 1303877 (F5OS-A) 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 | | |feature |
+————+——+————–+———-+———-+——+————-+
|BIG-IP (all |All |None |Not |Not |None |None |
|modules) | | |applicable|vulnerable| | |
+————+——+————–+———-+———-+——+————-+
|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.
F5OS
+——-+——+—————-+———-+———-+——-+—————+
| | |Versions known |Fixes | |CVSSv3 |Vulnerable |
|Product|Branch|to be vulnerable|introduced|Severity |score^2|component or |
| | |^1 |in | | |feature |
+——-+——+—————-+———-+———-+——-+—————+
|F5OS-A |1.x |1.3.0 – 1.3.2 |1.5.0 |Medium |4.7 |CPU |
+——-+——+—————-+———-+———-+——-+—————+
|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 | | |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.
Other products
+——-+——+—————–+———-+———-+——+—————+
| | |Versions known to|Fixes | |CVSSv3|Vulnerable |
|Product|Branch|be vulnerable^1 |introduced|Severity |score |component or |
| | | |in | | |feature |
+——-+——+—————–+———-+———-+——+—————+
|Traffix|All |None |Not |Not |None |None |
|SDC | | |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.
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
You can mitigate this vulnerability by restricting access to the affected F5
product (on the host OS and in a container or tenant) to only 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/
iQIVAwUBZK4Q5MkNZI30y1K9AQieTxAAm0vtJatldIf941ZHAOj60pIt7m5TiSQX
M8irj/JwpM7aFrUy9+laGf33+EU8km7hl/Ab7Jyjfu7fIOGTp0yCZY+ckugCJyFD
bql4fB2C1H43hLOZyTA0fi8JicRUkqowvxhaNGERMBFuYHY7Jv12D4LHDd5Llgxa
svsABC5ERyNMsjOSYcZBO9sdRPbuF+jm3Xa+wNa2Eqn1r4m17Bg9GgnAmiI+MdoO
J1O+Htjt5uIbUbeMJZEkbF0adtGycXgGeXKYriAR99Xp1FTDZGGubOiIO089/IgL
M2pUOwQ2023SFwbN+wgGjnC4Tpq5GhbPDih1e7kUogdgoAX50FxnIyjgSbFUMWb0
nQ463MEbcArZ31Fo0qIvzl1cI6N8toW+yDhwI9jwCRHDCysfRege9MNK1M95dWoF
yiZDSYfHOjDV9Wn+DSFkuD49CGs9EOZDip3SOjGTSnG6KYiJ8utJnOKoy6pLqxyY
3WWjZ9Yt+ydZaBhGWn1jNn/zhNLYOpmum+hxGDrSpc8nShxPF2Z2o9ZpfxDoYEwP
a2lVhfE49MOuElx1xYrkc+XBJ+GgsbTD5iv7pF6Gyv99nB31iYZO/I5efA1yZuMO
sbnMK6JitljVQHd08I3FYU/HYr0gU+ZiGwVq3WOi+zj1oi0z1EYsYjsazOXff8wV
PCGTaaAUf7I=
=V0Fp
—–END PGP SIGNATURE—–
Source: Read More
Security Bulletins