Protect yourself against future threats.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
===========================================================================
AUSCERT External Security Bulletin Redistribution
ESB-2023.0654.2
K83284425: iControl REST and tmsh vulnerability CVE-2023-22326
13 July 2023
===========================================================================
AusCERT Security Bulletin Summary
---------------------------------
Product: F5 BIG-IP (all modules)
F5 BIG-IQ Centralized Management
Publisher: F5 Networks
Operating System: Network Appliance
Resolution: Patch/Upgrade
CVE Names: CVE-2023-22326
Original Bulletin:
https://my.f5.com/manage/s/article/K83284425
Revision History: July 13 2023: Vendor updated advisory
February 6 2023: Initial Release
- --------------------------BEGIN INCLUDED TEXT--------------------
K83284425: iControl REST and tmsh vulnerability CVE-2023-22326
Published Date: Feb 1, 2023
Updated Date: Jul 12, 2023
Security Advisory Description
Incorrect permission assignment vulnerabilities exist in the iControl REST and
TMOS shell (tmsh) dig command which may allow an authenticated attacker with
resource administrator role privilege to view sensitive information. (
CVE-2023-22326)
Impact
An authenticated attacker with resource administrator role privilege may
exploit these vulnerabilities by sending a crafted request remotely through
iControl REST and locally through a crafted tmsh command. If the exploit is
successful, an attacker can view sensitive information. There is no data plane
exposure; this is a control plane issue only.
Security Advisory Status
F5 Product Development has assigned ID 1073005 (BIG-IP) to this vulnerability.
This issue has been classified as CWE-732: Incorrect Permission Assignment for
Critical Resource.
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 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 |17.1.0 | | | |
| | | |17.0.0.2 | | | |
| +------+-------------+----------+ | | |
| |16.x |16.1.0 - |16.1.3.3 | | | |
| | |16.1.3 | | | | |
| +------+-------------+----------+ | |iControl REST |
|BIG-IP (all |15.x |15.1.0 - |15.1.8.1 |Medium |4.9 |and tmsh dig |
|modules) | |15.1.8 | | | |command |
| +------+-------------+----------+ | | |
| |14.x |14.1.0 - |14.1.5.3 | | | |
| | |14.1.5 | | | | |
| +------+-------------+----------+ | | |
| |13.x |13.1.0 - |Will not | | | |
| | |13.1.5 |fix | | | |
+------------+------+-------------+----------+----------+------+--------------+
|BIG-IP SPK |All |None |Not |Not |None |None |
| | | |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 AskF5, 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 AskF5, 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 AskF5, and it is
possible that the document may be removed without our knowledge.
Other products
+-------+------+----------------+----------+----------+-------+---------------+
| | |Versions known |Fixes | |CVSSv3 |Vulnerable |
|Product|Branch|to be vulnerable|introduced|Severity |score^2|component or |
| | |^1 |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.
^2The CVSSv3 score link takes you to a resource outside of AskF5, 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
If it is not possible to update quickly, you can use the following sections as
temporary configuration mitigations until updating is complete.
o Mitigate iControl REST endpoint: These mitigations restrict access to
iControl REST to only trusted networks or devices, thereby limiting the
attack surface.
? Block iControl REST access through the self IP address
? Block iControl REST access through the management interface
o Mitigate TMOS shell (tmsh) command: As this attack is conducted by
legitimate, authenticated users, there is no viable mitigation that also
allows users access to the BIG-IP system. The only mitigation is to remove
access for users who are not completely trusted.
These mitigations restrict access to the BIG-IP command line through SSH to
only trusted networks or devices, thereby limiting the attack surface.
? Block SSH access through self IP addresses
? Block SSH access through the management interface
Mitigate iControl REST endpoint
Block iControl REST access through the self IP address
You can block all access to the iControl REST interface of your BIG-IP system
through self IP addresses. To do so, you can change the Port Lockdown setting
to Allow None for each self IP address in the system. If you must open any
ports, you should use the Allow Custom option, taking care to disallow access
to iControl REST. By default, iControl REST listens on TCP port 443 or TCP port
8443 on single NIC BIG-IP VE instances. If you modified the default port,
ensure that you disallow access to the alternate port you configured.
Note: Performing this action prevents all access to the Configuration utility
and iControl REST using the self IP address. These changes may also impact
other services, including breaking high availability (HA) configurations.
Before you make changes to the configuration of your self IP addresses. F5
strongly recommends that you refer to the following articles:
o K17333: Overview of port lockdown behavior (12.x - 17.x)
o K13092: Overview of securing access to the BIG-IP system
o K31003634: The Configuration utility of the Single-NIC BIG-IP Virtual
Edition now defaults to TCP port 8443
o K51358480: The single-NIC BIG-IP VE may erroneously revert to the default
management httpd port after a configuration reload
If you must expose port 443 on your self IP addresses and want to restrict
access to specific IP ranges, you may consider using the packet filtering
functionality built into the BIG-IP system. For more information, refer to the
following article:
o K13383: Configure CIDR Network Addresses for the BIG-IP packet filter
Block iControl REST access through the management interface
To mitigate this vulnerability for affected F5 products, you should restrict
management access only to trusted users and devices over a secure network. For
more information about securing access to BIG-IP systems, refer to the
following articles:
o K13092: Overview of securing access to the BIG-IP system
o K46122561: Restrict access to the BIG-IP management interface using network
firewall rules
o K69354049: Use iptables to restrict access to the BIG-IP management
interface for Configuration utility and iControl REST services
Mitigate TMOS shell (tmsh) command:
Block SSH access through self IP addresses
You can block all access to the command line through SSH of your BIG-IP system
using self IP addresses. To do so, you can change the Port Lockdown setting to
Allow None for each self IP address on the system. If you must open any ports,
you should use the Allow Custom option, taking care to block access to SSH. By
default, the SSH service listens on TCP port 22.
Note: Performing this action prevents all access to SSH using the self IP
address. These changes may also impact other services.
Before you make changes to the configuration of your self IP addresses, F5
strongly recommends that you refer to the following articles:
o K17333: Overview of port lockdown behavior (12.x - 17.x)
o K13092: Overview of securing access to the BIG-IP system
If you must expose port 22 on your self IP addresses and want to restrict
access to specific IP ranges, you may consider using the packet filtering
functionality built into the BIG-IP system. For more information, refer to the
following article:
o K13383: Configure CIDR Network Addresses for the BIG-IP packet filter
Block SSH access through the management interface
You should restrict management access to F5 products to only trusted users and
devices over a secure network. For more information about securing access to
BIG-IP systems, refer to the following articles:
o K13092: Overview of securing access to the BIG-IP system
o K46122561: Restrict access to the BIG-IP management interface using network
firewall rules
Acknowledgements
F5 acknowledges Guillaume Goessel of Aon's Cyber Labs for bringing this issue
to our attention and following the highest standards of coordinated disclosure.
Related Content
o K41942608: Overview of 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 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.
===========================================================================
-----BEGIN PGP SIGNATURE-----
Comment: https://auscert.org.au/gpg-key/
iQIVAwUBZK+RFMkNZI30y1K9AQg/jxAAq3nuLuCCcmEQZ6KBMBkZOE27bcEqN/WJ
ZdOWsyL5IPQ4bbMpX4d8MF+MSEuqeWttzHjPKMkmaldQQ5LwFfHx99EjFwSzGJV/
70cUgQZ2cbDTD93piVoIprKv0kzYon1zXpUV3cjvmnokDvYogYK0p1wVNMhUNyN7
Qk0NRkUzoEEzqQZztAYuTCUuCcvjYOkxgwSjgWlJ3W71Z0WDRiE6ECMfESJqiKZn
GqjqRJWfmwJdIX5JX2ZFZptbDLolKZufK8aguRGw6Oz/kNPFTDbiGWXY32D89kbg
poues98+CARAo2tRUDNMIXXBD6Oxq7vPn+4kfPOShzCsG9Wch3Q1rQjPzwinklO3
DL7e2ZM92G2EXugUvzjvjS4C8Vyh4fYHBMSJLwdxdZBnhzWuepxGinBzqfA4Kjxa
/fSYNM1umE4xY/yCXG1732R0S9EZHyeMbF04ZHpsYcJa4HbZeWpUwb0lW80yGn/Y
neHYRq3VRVBu5B2nWCR1mZbpLjyztsGiTGajgGWlYhgsi3fkVcf3w7UN8RRpMXyw
uXetNj3G+anpBcbYATiDdN5OYu8CiC9LuYIFWfgXvvIrRymhqoxpRQcATQ6RDvTM
Ri5FRemzHh8dhgCXq9TCOBmIo9tpmdMou1DypYQvaQJzBFKdfUUHpf+hLFVQq9a7
BmR6nadaVvw=
=BOGW
-----END PGP SIGNATURE-----