Protect yourself against future threats.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
===========================================================================
AUSCERT External Security Bulletin Redistribution
ESB-2022.5996.2
K94221585: iControl SOAP vulnerability CVE-2022-41622
21 November 2022
===========================================================================
AusCERT Security Bulletin Summary
---------------------------------
Product: BIG-IP
BIG-IQ
Publisher: F5 Networks
Operating System: Network Appliance
Resolution: Mitigation
CVE Names: CVE-2022-41622
Original Bulletin:
https://support.f5.com/csp/article/K94221585
Comment: CVSS (Max): 8.8 CVE-2022-41622 (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/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:R/S:U/C:H/I:H/A:H
Revision History: November 21 2022: Vendor added further information to the Recommended Actions
November 17 2022: Initial Release
- --------------------------BEGIN INCLUDED TEXT--------------------
K94221585: iControl SOAP vulnerability CVE-2022-41622
Original Publication Date: 17 Nov, 2022
Latest Publication Date: 20 Nov, 2022
Security Advisory Description
BIG-IP and BIG-IQ are vulnerable to cross-site request forgery (CSRF) attacks
through iControl SOAP. (CVE-2022-41622)
Impact
An attacker may trick users who have at least resource administrator role
privilege and are authenticated through basic authentication in iControl SOAP
into performing critical actions. An attacker can exploit this vulnerability
only through the control plane, not through the data plane. If exploited, the
vulnerability can compromise the complete system.
Security Advisory Status
F5 Product Development has assigned ID 1143073 (BIG-IP) and 1143073-6 (BIG-IQ)
to this vulnerability. This issue has been classified as CWE-352: Cross-Site
Request Forgery (CSRF).
To determine if your product and version have been evaluated for this
vulnerability, refer to the Applies to (see versions) 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 |
+------------+------+--------------+----------+----------+------+-------------+
| |17.x |17.0.0 |None^3 | | | |
| +------+--------------+----------+ | | |
| |16.x |16.1.0 - |None^3 | | | |
| | |16.1.3 | | | | |
| +------+--------------+----------+ | | |
|BIG-IP (all |15.x |15.1.0 - |None^3 | | | |
|modules) | |15.1.8 | |High |8.8 |iControl SOAP|
| +------+--------------+----------+ | | |
| |14.x |14.1.0 - |None^3 | | | |
| | |14.1.5 | | | | |
| +------+--------------+----------+ | | |
| |13.x |13.1.0 - |None^3 | | | |
| | |13.1.5 | | | | |
+------------+------+--------------+----------+----------+------+-------------+
|BIG-IP SPK |All |None |Not |Not |None |None |
| | | |applicable|vulnerable| | |
+------------+------+--------------+----------+----------+------+-------------+
|BIG-IQ |8.x |8.0.0 - 8.2.0 |None | | | |
|Centralized +------+--------------+----------+High |8.8 |iControl SOAP|
|Management |7.x |7.1.0 |None | | | |
+------------+------+--------------+----------+----------+------+-------------+
^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.
^3F5 has fixed this issue in an engineering hotfix that is available for
supported versions of the BIG-IP system. Customers affected by this issue can
request a hotfix for the latest supported versions of BIG-IP from F5 Support.
To resolve this vulnerability, after installing the hotfix to one of the BIG-IP
releases listed in the previous table, you must also disable Basic
Authentication for iControl SOAP.
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.
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 table).
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.
Important: Blocking iControl SOAP IP addresses and/or installing the HF and
disabling basic auth for iControl SOAP will impact adding new devices to a
device trust.
BIG-IP
To eliminate this vulnerability in the BIG-IP system, after installing a
version listed in the Fixes introduced in column, you must disable Basic
Authentication for iControl SOAP. To do so, perform the following procedure:
Impact of procedure: Performing the following procedure should not have a
negative impact on your system.
1. Log in to the Traffic Management Shell (tmsh) by entering the following
command:
tmsh
2. Disable Basic Authentication for iControl SOAP by entering the following
command:
modify sys db icontrol.basic_auth value disable
3. Save the configuration by entering the following command:
save sys config
Note: Disabling db key icontrol.basic_auth will only disable basic auth for
iControl SOAP. It will not disable basic auth functionality of iControl
REST.
Mitigation
To mitigate this vulnerability, you can use a unique and isolated web browser
when managing the BIG-IP or BIG-IQ system.
This attack cannot be prevented if you have authenticated to iControl SOAP in
the web browser with basic authentication. This authentication mechanism is
uncommon and is different from using the login page for the Configuration
utility. F5 recommends that you do not authenticate with basic authentication
in the web browser. If an authentication window for basic authentication pops
up on the web browser, do not provide credentials.
If you follow best practices in securing access to the management interface and
self IP addresses of BIG-IP and BIG-IQ systems, you help to minimize the attack
surface. Review the following articles for guidance:
For Self IP addresses
o K13092: Overview of securing access to the BIG-IP system
o K17333: Overview of port lockdown behavior (12.x - 17.x)
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
o K39403510: Managing the port lockdown configuration on the BIG-IQ system
For Management interface
o K46122561: Restricting access to the management interface using network
firewall rules
o K69354049: Restricting access to the BIG-IP management interface for
Configuration Utility and iControl REST services using iptables
o K92748202: Restricting access to the BIG-IQ management interface using
network firewall rules
Note: For BIG-IQ 7.x, secure the management interface by using an external
packet filtering device such as the BIG-IP Advanced Firewall Manager (AFM).
BIG-IP mitigation
For the BIG-IP system only, restrict access to the system's iControl SOAP API
to only trusted users. If you are not using the iControl SOAP API, then you can
disable all access by setting the iControl SOAP API allowed list to an empty
list. To do so, perform the following procedure:
1. Log in to tmsh by entering the following command:
tmsh
2. Remove all IP addresses or range of IP addresses from the list of allowed
addresses by entering the following command:
modify /sys icontrol-soap allow replace-all-with { }
3. Save the change by entering the following command:
save /sys config
For more information about limiting access to trusted users, refer to K17459:
Restricting access to the iControl SOAP API by source IP address.
BIG-IQ mitigation
For the BIG-IQ system only, restrict the iControl SOAP access to localhost
(127.0.0.1) by changing the webd configuration. To do so, perform the following
procedure:
Impact of procedure: The BIG-IQ user interface may be momentarily disrupted
while the webd service restarts.
1. Log in to the command line of the affected BIG-IQ system as the root user.
2. Back up a copy of the webd configuration by entering the following command:
cp -p /etc/webd/webd.conf /etc/webd/webd.conf.K94221585
3. Have a text editor such as vi or nano available to edit the webd
configuration.
4. There are two iControl FastCGI endpoint (location /iControl/
iControlPortal.cgi) configurations; one is under the server configuration
stanza listening for port 80, and the other is located under the server
configuration stanza listening for port 443 and is enabled with SSL. The
one under the port 80 server is already restricted to localhost (127.0.0.1)
by default. Restrict the one under the SSL server. The starting of the SSL
server configuration stanza should appear similar to the following example:
server {
listen [::]:443 ipv6only=on ssl;
listen *:443 ssl;
}
5. Locate the iControl FastCGI endpoint configuration under this SSL server;
it should appear similar to the following example:
# iControl FastCGI endpoint
location /iControl/iControlPortal.cgi {
access_by_lua_file /usr/lib/webd/lua/icauth.lua;
fastcgi_pass 127.0.0.1:8202;
fastcgi_pass_header X-IControl-Session;
fastcgi_pass_request_body on;
fastcgi_param QUERY_STRING $query_string;
fastcgi_param REQUEST_METHOD $request_method;
fastcgi_param CONTENT_TYPE $content_type;
fastcgi_param CONTENT_LENGTH $content_length;
fastcgi_param SCRIPT_NAME '/iControl/iControlPortal.cgi';
}
6. Add the following two lines of configuration to this iControl FastCGI
endpoint configuration:
allow 127.0.0.1;
deny all;
7. After you add the two lines of configuration, the iControl FastCGI endpoint
configuration should appear similar to the following example:
# iControl FastCGI endpoint
location /iControl/iControlPortal.cgi {
allow 127.0.0.1;
deny all;
access_by_lua_file /usr/lib/webd/lua/icauth.lua;
fastcgi_pass 127.0.0.1:8202;
fastcgi_pass_header X-IControl-Session;
fastcgi_pass_request_body on;
fastcgi_param QUERY_STRING $query_string;
fastcgi_param REQUEST_METHOD $request_method;
fastcgi_param CONTENT_TYPE $content_type;
fastcgi_param CONTENT_LENGTH $content_length;
fastcgi_param SCRIPT_NAME '/iControl/iControlPortal.cgi';
}
8. Save the changes and exit the text editor.
9. To effect the change, you must restart the webd service. To do so, enter
the following command:
tmsh restart /sys service webd
Acknowledgements
F5 acknowledges Ron Bowes of Rapid7 for bringing this issue to our attention
and following the highest standards of coordinated disclosure.
Supplemental Information
o K41942608: Overview of security advisory articles
o K4602: Overview of the F5 security vulnerability response policy
o K4918: Overview of the F5 critical issue hotfix policy
o K8986: F5 product support policies
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 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
o K26814434: How to determine if a BIG-IP system is using iControl SOAP
o K80291425: What is a Cross-site Request Forgery (CSRF) attack
- --------------------------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/
iQIVAwUBY3sOpMkNZI30y1K9AQgMMg//euUjZdyi5Nt1JdMSi7nz71o4jzhGXRrl
K1izIQOAbdvpBVY6+wjTBZO8OLQrwUOrfyi2KCv3+Cw9TswhdlYIb+5YXD4paMaG
I+kBNkpFrTtDuGDTThoudnVnKQNJv+4uKBjaMMdCIBtI2OHpnjcjeyRpGSBfdSNe
LqJVpfeHW/LaBfTzUocGc47OWnXgHS91ZFvyJRqSuHXr/rvbqEnOQX0cWF2PN5u0
6zJP2LxfVzCz3j2V2HS0oh5xKWLphpysQQUYuZNpn3d7o0rBkKK+e172d3cM2t0H
HRCQGd76KoZLzmSsJE+caS7NsrS+SbrTbZEtKiPvKNBYjnJ1RLshgMEOazKnQlHl
aB5/a2BR3/M2jnwZX0NxgIDNik/6EwOI+EjIwBIUbfMQ5pThkqkERiUBK6it7HzU
tz/DWY7XD/gO8NCRnYXV9/z3/c3P9zJznwEbqs9q3xzAge1yO28j7HQzK2zNoApW
kh/rrk+ij1c8irgq1RwCi5jeOEfWTs4m6pi9cT/OHVU8ue/lE1dRi2AuPdDOOb31
VNouPqMRQMYv7A+vJSuIBiv1Z4Ld1AOkHYwTGv8juDi+OcYOPQVoqU0WN5PtV4fe
dKRCJc0QhUr7j4Se6sYZexIP3WWHtHVhwSZmzQVfv+JdacWwDxS1QlWlxoV2YdNb
w2XcTyP32x0=
=HlTy
-----END PGP SIGNATURE-----