Protect yourself against future threats.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
===========================================================================
AUSCERT External Security Bulletin Redistribution
ESB-2021.2862
Advanced WAF and BIG-IP ASM vulnerabilities
25 August 2021
===========================================================================
AusCERT Security Bulletin Summary
---------------------------------
Product: BIG-IP Advanced WAF
BIG-IP ASM
Publisher: F5 Networks
Operating System: Network Appliance
Impact/Access: Administrator Compromise -- Existing Account
Denial of Service -- Remote/Unauthenticated
Reduced Security -- Remote/Unauthenticated
Resolution: Patch/Upgrade
CVE Names: CVE-2021-23053 CVE-2021-23050 CVE-2021-23029
CVE-2021-23028
Original Bulletin:
https://support.f5.com/csp/article/K36942191
https://support.f5.com/csp/article/K52420610
https://support.f5.com/csp/article/K30291321
https://support.f5.com/csp/article/K49549213
https://support.f5.com/csp/article/K00602225
https://support.f5.com/csp/article/K44553214
https://support.f5.com/csp/article/K42051445
https://support.f5.com/csp/article/K05314769
https://support.f5.com/csp/article/K41351250
https://support.f5.com/csp/article/K05391775
https://support.f5.com/csp/article/K30150004
Comment: This bulletin contains eleven (11) F5 Networks security advisories.
- --------------------------BEGIN INCLUDED TEXT--------------------
K36942191: Advanced WAF and BIG-IP ASM MySQL database vulnerability
CVE-2021-23053
Original Publication Date: 24 Aug, 2021
Security Advisory Description
When the brute force protection feature of ASM/Adv WAF is enabled on a virtual
server and the virtual server is under brute force attack, the MySQL database
may run out of disk space due to lack of row limit on undisclosed tables in the
MYSQL database. (CVE-2021-23053)
Impact
When attackers exploit this vulnerability, the MySQL database consumes more
storage space than expected. As a result, the related configuration and
reporting services in the Configuration utility, the TMOS Shell (tmsh), and
iControl REST may fail to function as expected. Though the attack originates in
the data plane, the attack impacts only the control plane.
Security Advisory Status
F5 Product Development has assigned ID 825413 (BIG-IP) to this vulnerability.
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 table. For more
information about security advisory versioning, refer to K51812227:
Understanding security advisory versioning.
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. Additionally, software
versions preceding those listed in the following table have reached the End of
Technical Support (EoTS) phase of their lifecycle and are no longer evaluated
for security issues. For more information, refer to the Security hotfixes
section of K4602: Overview of the F5 security vulnerability response policy.
+------------+------+--------------+----------+----------+------+-------------+
| | |Versions known|Fixes | |CVSSv3|Vulnerable |
|Product |Branch|to be |introduced|Severity |score^|component or |
| | |vulnerable^1 |in | |2 |feature |
+------------+------+--------------+----------+----------+------+-------------+
| |16.x |None |16.0.0 | | | |
| +------+--------------+----------+ | | |
| |15.x |15.1.0 - |15.1.3 | | | |
| | |15.1.2 | | | | |
| +------+--------------+----------+ | | |
| |14.x |14.1.0 - |14.1.3.1 | | | |
|BIG-IP | |14.1.3 | | | |BIG-IP ASM |
|(Advanced +------+--------------+----------+Low |3.7 |MySQL |
|WAF, ASM) |13.x |13.1.0 - |13.1.3.6 | | |database |
| | |13.1.3 | | | | |
| +------+--------------+----------+ | | |
| |12.x |None |Not | | | |
| | | |applicable| | | |
| +------+--------------+----------+ | | |
| |11.x |None |Not | | | |
| | | |applicable| | | |
+------------+------+--------------+----------+----------+------+-------------+
| |16.x |None |Not | | | |
| | | |applicable| | | |
| +------+--------------+----------+ | | |
| |15.x |None |Not | | | |
| | | |applicable| | | |
| +------+--------------+----------+ | | |
| |14.x |None |Not | | | |
|BIG-IP (all | | |applicable|Not | | |
|other +------+--------------+----------+vulnerable|None |None |
|modules) |13.x |None |Not | | | |
| | | |applicable| | | |
| +------+--------------+----------+ | | |
| |12.x |None |Not | | | |
| | | |applicable| | | |
| +------+--------------+----------+ | | |
| |11.x |None |Not | | | |
| | | |applicable| | | |
+------------+------+--------------+----------+----------+------+-------------+
| |8.x |None |Not | | | |
| | | |applicable| | | |
|BIG-IQ +------+--------------+----------+ | | |
|Centralized |7.x |None |Not |Not |None |None |
|Management | | |applicable|vulnerable| | |
| +------+--------------+----------+ | | |
| |6.x |None |Not | | | |
| | | |applicable| | | |
+------------+------+--------------+----------+----------+------+-------------+
|F5OS |1.x |None |Not |Not |None |None |
| | | |applicable|vulnerable| | |
+------------+------+--------------+----------+----------+------+-------------+
|Traffix SDC |5.x |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.
^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 upgrading 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.
Mitigation
If you are unable to upgrade and require mitigation steps, contact F5 Support.
Acknowledgements
This issue was discovered internally by F5.
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 software lifecycle policy
o K9502: BIG-IP hotfix and point release matrix
o K13123: Managing BIG-IP product hotfixes (11.x - 16.x)
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
- --------------------------------------------------------------------------------
K52420610: Advanced WAF and BIG-IP ASM TMUI vulnerability CVE-2021-23029
Original Publication Date: 24 Aug, 2021
Security Advisory Description
Insufficient permission checks may allow authenticated users with guest
privileges to perform Server-Side Request Forgery (SSRF) attacks through F5
Advanced Web Application Firewall (WAF) and the BIG-IP ASM Configuration
utility. (CVE-2021-23029)
Impact
An attacker with network access to the management interface and authenticated
with guest privileges may be able to perform an SSRF attack.
Security Advisory Status
F5 Product Development has assigned ID 979081 (BIG-IP) to this vulnerability.
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 table. For more
information about security advisory versioning, refer to K51812227:
Understanding security advisory versioning.
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. Additionally, software
versions preceding those listed in the following table have reached the End of
Technical Support (EoTS) phase of their lifecycle and are no longer evaluated
for security issues. For more information, refer to the Security hotfixes
section of K4602: Overview of the F5 security vulnerability response policy.
+------------+------+--------------+----------+----------+------+-------------+
| | |Versions known|Fixes | |CVSSv3|Vulnerable |
|Product |Branch|to be |introduced|Severity |score^|component or |
| | |vulnerable^1 |in | |2 |feature |
+------------+------+--------------+----------+----------+------+-------------+
| |16.x |16.0.0 - |16.1.0 | | | |
| | |16.0.1 |16.0.1.2 | | | |
| +------+--------------+----------+ | | |
| |15.x |None |Not | | | |
| | | |applicable| | | |
| +------+--------------+----------+ | | |
| |14.x |None |Not | | | |
|BIG-IP | | |applicable| | | |
|(Advanced +------+--------------+----------+High |7.5 |TMUI |
|WAF, ASM) |13.x |None |Not | | | |
| | | |applicable| | | |
| +------+--------------+----------+ | | |
| |12.x |None |Not | | | |
| | | |applicable| | | |
| +------+--------------+----------+ | | |
| |11.x |None |Not | | | |
| | | |applicable| | | |
+------------+------+--------------+----------+----------+------+-------------+
| |16.x |None |Not | | | |
| | | |applicable| | | |
| +------+--------------+----------+ | | |
| |15.x |None |Not | | | |
| | | |applicable| | | |
| +------+--------------+----------+ | | |
| |14.x |None |Not | | | |
|BIG-IP (all | | |applicable|Not | | |
|other +------+--------------+----------+vulnerable|None |None |
|modules) |13.x |None |Not | | | |
| | | |applicable| | | |
| +------+--------------+----------+ | | |
| |12.x |None |Not | | | |
| | | |applicable| | | |
| +------+--------------+----------+ | | |
| |11.x |None |Not | | | |
| | | |applicable| | | |
+------------+------+--------------+----------+----------+------+-------------+
| |7.x |None |Not | | | |
|BIG-IQ | | |applicable|Not | | |
|Centralized +------+--------------+----------+vulnerable|None |None |
|Management |6.x |None |Not | | | |
| | | |applicable| | | |
+------------+------+--------------+----------+----------+------+-------------+
|F5OS |1.x |None |Not |Not |None |None |
| | | |applicable|vulnerable| | |
+------------+------+--------------+----------+----------+------+-------------+
|Traffix SDC |5.x |None |Not |Not |None |None |
| | | |applicable|vulnerable| | |
+------------+------+--------------+----------+----------+------+-------------+
^1F5 only evaluates software versions that have not yet reached the End of
Technical Support (EoTS) phase of their lifecycle.
^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 upgrading to a version listed
in the Fixes introduced in column. If the table lists only an older version
than what you are currently running, or does not list a non-vulnerable version,
then no upgrade candidate currently exists.
Mitigation
As this attack is conducted by legitimate, authenticated users, there is no
viable mitigation while still allowing the user access to the Configuration
utility. The only mitigation is to remove access for users who are not
completely trusted.
Until it is possible to install a fixed version, you can use the following
sections as temporary mitigations. These mitigations restrict access to the
Configuration utility to only trusted networks or devices, thereby limiting the
attack surface.
o Block Configuration utility access through self IP addresses
o Block Configuration utility access through the management interface
Block Configuration utility access through self IP addresses
You can block all access to the Configuration utility 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 disallow access to the
Configuration utility. By default, the Configuration utility listens on TCP
port 443. Alternatively, you can configure a custom port.
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 - 16.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 in to the BIG-IP system. For more information, refer to the
following article:
o K13383: Configuring CIDR Network Addresses for the BIG-IP packet filter
Block Configuration utility access through the management interface
To mitigate this vulnerability for affected F5 products, you should restrict
management access only to trusted users and devices to F5 products over a
secure network. For more information about securing access to BIG-IP systems,
refer to the following articles:
o K13309: Restricting access to the Configuration utility by source IP
address (11.x - 16.x)
o K13092: Overview of securing access to the BIG-IP system
o K46122561: Restricting access to the management interface using network
firewall rules
Acknowledgements
This issue was discovered internally by F5.
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 software lifecycle policy
o K9502: BIG-IP hotfix and point release matrix
o K13123: Managing BIG-IP product hotfixes (11.x - 16.x)
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
- --------------------------------------------------------------------------------
K30291321: Advanced WAF and BIG-IP ASM attack signature check may fail to detect
and block illegal requests for a case-insensitive policy
Original Publication Date: 24 Aug, 2021
Security Advisory Description
The F5 Advanced Web Application Firewall (WAF) and BIG-IP ASM attack signature
check may fail to detect and block illegal requests. This issue occurs when all
of the following conditions are met:
o The affected policy is configured as case insensitive (the Policy is case
sensitive setting is disabled)
Note: You can configure the Policy is case sensitive setting only when you
first create a security policy. By default, this setting is enabled when
you first create the security policy. You cannot change this setting after
you create the security policy.
o One of the words from the attack signature matches that of the parameter
name.
o The word from the attack signature is case sensitive; it does not have the
nocase modifier in the signature.
Impact
The attack signature check fails to detect and block illegal requests as
expected of a security policy configured as case insensitive.
Symptoms
As a result of this issue, the Advanced WAF/BIG-IP ASM system does not block
some requests.
Security Advisory Status
F5 Product Development has assigned ID 968421 to this issue. F5 has confirmed
that this issue exists in the products listed in the Applies to (see versions)
box, located in the upper-right corner of this article. For information about
releases, point releases, or hotfixes that resolve this issue, refer to the
following table.
Note: F5 only evaluates software versions that have not yet reached the End of
Technical Support (EoTS) phase of their lifecycle.
+------------------+-----------------+----------------------------------------+
|Type of fix |Fixes introduced |Related articles |
| |in | |
+------------------+-----------------+----------------------------------------+
|Release |16.1.0 |K2200: Most recent versions of F5 |
| |12.1.6 |software |
+------------------+-----------------+----------------------------------------+
| |16.0.1.2 | |
|Point release/ |15.1.2.1 |K9502: BIG-IP hotfix and point release |
|hotfix |14.1.4.2 |matrix |
| |13.1.4.1 | |
| |11.6.5.3 | |
+------------------+-----------------+----------------------------------------+
Recommended Actions
Workaround
If you created a custom attack signatures that matches the parameter name in a
case-insensitive policy, you can add the nocase modifier to the custom
signature. For more information about the nocase modifier, refer to the
Signature Syntax chapter of the BIG-IP Application Security Manager: Attack and
Bot Signatures guide.
Note: For information about how to locate F5 product guides, refer to
K12453464: Finding product documentation on AskF5.
Supplemental Information
o K51812227: Understanding security advisory versioning
o K41942608: Overview of AskF5 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 software lifecycle policy
o K9502: BIG-IP hotfix and point release matrix
o K13123: Managing BIG-IP product hotfixes (11.x - 16.x)
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
- --------------------------------------------------------------------------------
K49549213: Advanced WAF and BIG-IP ASM brute force mitigation may fail when
receiving a specially crafted request
Original Publication Date: 24 Aug, 2021
Security Advisory Description
F5 Advanced Web Application Firewall (WAF) and BIG-IP ASM brute force
mitigation may fail. This issue occurs when all of the following conditions are
met:
o A security policy is configured with a login page using basic
authentication as its authentication type.
o The affected Advanced WAF and BIG-IP ASM systems receive a specially
crafted request for the login page.
Impact
The Advanced WAF and BIG-IP ASM systems fail to stop brute force attacks on the
protected login page.
Symptoms
The login page is unprotected from brute force attacks.
Security Advisory Status
F5 Product Development has assigned ID 928685 to this issue. F5 has confirmed
that this issue exists in the products listed in the Applies to (see versions)
box, located in the upper-right corner of this article. For information about
releases, point releases, or hotfixes that resolve this issue, refer to the
following table.
Note: F5 only evaluates software versions that have not yet reached the End of
Technical Support (EoTS) phase of their lifecycle.
+------------------+-----------------+----------------------------------------+
|Type of fix |Fixes introduced |Related articles |
| |in | |
+------------------+-----------------+----------------------------------------+
|Release |16.1.0 |K2200: Most recent versions of F5 |
| |15.1.3 |software |
+------------------+-----------------+----------------------------------------+
|Point release/ |16.0.1.2 |K9502: BIG-IP hotfix and point release |
|hotfix |14.1.4.2 |matrix |
| |13.1.4.1 | |
+------------------+-----------------+----------------------------------------+
Recommended Actions
Mitigation
To mitigate this security issue, you can use the following iRule to attempt to
extract the HTTP::username. When the decoding of the username fails (due to any
reason), the iRule will raise the custom violation
bad_auth_header_custom_violation:
when ASM_REQUEST_DONE
{
if { [catch { HTTP::username } ] } {
log local0. "ERROR: bad username";
ASM::raise bad_auth_header_custom_violation
}
}
To mitigate this security issues, perform the following procedures in sequence:
o Configure a custom violation
o Enable Advanced WAF and BIG-IP ASM iRule events
o Create the iRule and associate it with the virtual server
Configure a custom violation
For the iRule to work, you must configure the affected Advanced WAF and ASM
systems with a custom violation called bad_auth_header_custom_violation, and
set it to blocking. To configure a custom violation, perform the following
procedure:
Impact of procedure: Performing this procedure should not have a negative
impact on your system.
1. Log in to the Configuration utility of the affected BIG-IP Advanced WAF and
ASM systems.
2. Navigate to Security > Options > Application Security > Advanced
Configuration > Violations List.
3. Select User-Defined Violations.
4. Select Create.
5. Type bad_auth_header_custom_violation in the Violation Name setting.
6. Type a descriptive name for the Violation Title setting.
For example:
Bad Auth Header Custom Violation.
7. Select Input Violation for the Type setting.
8. Select a severity level most appropriate for your application environment
for the Severity setting.
9. Select HTTP Parser Attack for the Attack Type setting.
10. (Optional) Type a description in the Description setting.
11. Select Create to save the newly configured custom violation.
12. Navigate to Security > Application Security > Policy Building > Learning
and Blocking Settings.
13. Select your desired security policy in the Current edited policy drop-down.
14. Expand the Custom Violations section. You should observe the custom
violation you created in the previous steps listed in this section. Based
on the example in previous steps, you should see the Bad Auth Header Custom
Violation custom violation.
15. Select Alarm and/or Block as needed for this custom violation.
Note: Enabling Alarm allows the system to record requests that trigger the
violation in the Charts screen, as well as system/local/remote logs.
Enabling Block allows the system to block the request that trigger the
violation if the security policy enforcement mode is set to Blocking.
16. Select Save to save the changes.
17. Select Apply Policy to activate the change in the desired security policy.
Enable Advanced WAF and BIG-IP ASM iRule events
Before you configure the iRule to trigger the custom violation, you must enable
ASM iRule events for the security policy. To do so, perform one of the
following procedures, depending on your version of BIG-IP Advanced WAF and ASM:
Impact of procedure: Performing this procedure should not have a negative
impact on your system.
BIG-IP 15.1.x and later
1. Log in to the Configuration utility of the affected Advanced WAF and BIG-IP
ASM systems.
2. Navigate to Security > Application Security > Security Policies > Policies
List.
3. Select the name of the policy that you want to edit.
4. In Security Policy Configuration, select General Settings.
5. For the Trigger ASM iRule Events Mode setting, select Normal.
6. Select Save.
7. Select Apply Policy.
BIG-IP 14.x through 15.0.x
1. Log in to the Configuration utility of the affected Advanced WAF and BIG-IP
ASM systems.
2. Navigate to Security > Application Security > Security Policies > Policies
List.
3. Select the name of the policy that you want to edit.
4. In the Policy Properties tab, select Advanced.
5. For the Trigger ASM iRule Events setting, select Normal Mode.
6. Select Save Changes.
7. Select Apply.
BIG-IP 13.x and earlier
1. Log in to the Configuration utility of the affected Advanced WAF and BIG-IP
ASM systems.
2. Navigate to Security > Application Security > Policy > Policy Properties.
3. From the Current edited security policy list, select the policy that you
want to edit.
4. In the Policy Properties section, select Advanced.
5. For the Trigger ASM iRule Events setting, select Enabled.
6. Select Save.
7. Select Apply Policy.
Create the iRule and associate it with the virtual server
To create the iRule and associate it with the desired virtual server, perform
the following procedure:
Impact of procedure: Performing this procedure should not have a negative
impact on your system.
1. Log in to the Configuration utility of the affected Advanced WAF and BIG-IP
ASM system.
2. Navigate to Local Traffic > iRules > iRule List.
3. Select Create.
4. Type a name in the Name setting. For example, K49549213.
5. Copy the iRule and paste it into the Definition setting.
6. Select Finished to save the iRule.
7. Navigate to Local Traffic > Virtual Servers > Virtual Server List.
8. Select the name of the desired virtual server.
9. Select Resources.
10. Select Manage for the iRules section.
11. Select the iRule you have configured in previous steps from Available and
move it to Enabled by clicking <<.
12. Select Finished to save the change.
Supplemental Information
o K51812227: Understanding security advisory versioning
o K41942608: Overview of AskF5 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 software lifecycle policy
o K9502: BIG-IP hotfix and point release matrix
o K13123: Managing BIG-IP product hotfixes (11.x - 16.x)
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
- --------------------------------------------------------------------------------
K00602225: Advanced WAF and BIG-IP ASM vulnerability CVE-2021-23028
Original Publication Date: 24 Aug, 2021
Security Advisory Description
When JSON content profiles are configured for URLs as part of an F5 Advanced
Web Application Firewall (WAF)/BIG-IP ASM security policy and applied to a
virtual server, undisclosed requests may cause the BIG-IP ASM bd process to
terminate. (CVE-2021-23028)
Impact
Traffic is disrupted while the BIG-IP ASM bd process restarts. This
vulnerability allows a remote attacker to cause a denial-of-service (DoS) on
the BIG-IP system. There is no control plane exposure; this is a data plane
issue only.
Security Advisory Status
F5 Product Development has assigned ID 962341 (BIG-IP) to this vulnerability.
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 table. For more
information about security advisory versioning, refer to K51812227:
Understanding security advisory versioning.
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. Additionally, software
versions preceding those listed in the following table have reached the End of
Technical Support (EoTS) phase of their lifecycle and are no longer evaluated
for security issues. For more information, refer to the Security hotfixes
section of K4602: Overview of the F5 security vulnerability response policy.
+------------+------+--------------+----------+----------+------+-------------+
| | |Versions known|Fixes | |CVSSv3|Vulnerable |
|Product |Branch|to be |introduced|Severity |score^|component or |
| | |vulnerable^1 |in | |2 |feature |
+------------+------+--------------+----------+----------+------+-------------+
| |16.x |16.0.0 - |16.1.0 | | | |
| | |16.0.1 |16.0.1.2 | | | |
| +------+--------------+----------+ | | |
| |15.x |15.1.0 - |15.1.3.1 | | | |
| | |15.1.3 | | | | |
| +------+--------------+----------+ | | |
| |14.x |14.1.0 - |14.1.4.2 | | | |
|BIG-IP | |14.1.4 | | | |The bd |
|(Advanced +------+--------------+----------+High |7.5 |process |
|WAF. ASM) |13.x |13.1.0 - |13.1.4 | | | |
| | |13.1.3 | | | | |
| +------+--------------+----------+ | | |
| |12.x |None |Not | | | |
| | | |applicable| | | |
| +------+--------------+----------+ | | |
| |11.x |None |Not | | | |
| | | |applicable| | | |
+------------+------+--------------+----------+----------+------+-------------+
| |16.x |None |Not | | | |
| | | |applicable| | | |
| +------+--------------+----------+ | | |
| |15.x |None |Not | | | |
| | | |applicable| | | |
| +------+--------------+----------+ | | |
| |14.x |None |Not | | | |
|BIG-IP (all | | |applicable|Not | | |
|other +------+--------------+----------+vulnerable|None |None |
|modules) |13.x |None |Not | | | |
| | | |applicable| | | |
| +------+--------------+----------+ | | |
| |12.x |None |Not | | | |
| | | |applicable| | | |
| +------+--------------+----------+ | | |
| |11.x |None |Not | | | |
| | | |applicable| | | |
+------------+------+--------------+----------+----------+------+-------------+
| |8.x |None |Not | | | |
| | | |applicable| | | |
|BIG-IQ +------+--------------+----------+ | | |
|Centralized |7.x |None |Not |Not |None |None |
|Management | | |applicable|vulnerable| | |
| +------+--------------+----------+ | | |
| |6.x |None |Not | | | |
| | | |applicable| | | |
+------------+------+--------------+----------+----------+------+-------------+
|F5OS |1.x |None |Not |Not |None |None |
| | | |applicable|vulnerable| | |
+------------+------+--------------+----------+----------+------+-------------+
|Traffix SDC |5.x |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.
^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 upgrading 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.
Mitigation
o Configure systems with high availability (HA) clustering. For more
information, refer to K02234544: Manually setting up device service
clustering.
o Configure the HA table to take specific actions. For more information,
refer to K9231: Overview of BIG-IP daemon heartbeat failsafe.
Acknowledgements
This issue was discovered internally by F5.
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 software lifecycle policy
o K9502: BIG-IP hotfix and point release matrix
o K13123: Managing BIG-IP product hotfixes (11.x - 16.x)
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
- --------------------------------------------------------------------------------
K44553214: Advanced WAF and BIG-IP ASM vulnerability CVE-2021-23050
Original Publication Date: 24 Aug, 2021
Security Advisory Description
When a cross-site request forgery (CSRF)-enabled policy is configured on a
virtual server, an undisclosed HTML response may cause the BIG-IP ASM bd
process to terminate. (CVE-2021-23050)
Impact
Traffic is disrupted while the BIG-IP ASM bd process restarts. This
vulnerability allows a remote attacker to cause a denial-of-service (DoS) on
the BIG-IP system. There is no control plane exposure, this is a data plane
issue only.
Security Advisory Status
F5 Product Development has assigned ID 996753 (BIG-IP) to this vulnerability.
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 table. For more
information about security advisory versioning, refer to K51812227:
Understanding security advisory versioning.
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. Additionally, software
versions preceding those listed in the following table have reached the End of
Technical Support (EoTS) phase of their lifecycle and are no longer evaluated
for security issues. For more information, refer to the Security hotfixes
section of K4602: Overview of the F5 security vulnerability response policy.
+------------+------+--------------+----------+----------+------+-------------+
| | |Versions known|Fixes | |CVSSv3|Vulnerable |
|Product |Branch|to be |introduced|Severity |score^|component or |
| | |vulnerable^1 |in | |2 |feature |
+------------+------+--------------+----------+----------+------+-------------+
| |16.x |16.0.0 - |16.1.0 | | | |
| | |16.0.1 |16.0.1.2 | | | |
| +------+--------------+----------+ | | |
| |15.x |15.1.0 - |15.1.3.1 | | | |
| | |15.1.3 | | | | |
| +------+--------------+----------+ | | |
| |14.x |None |Not | | | |
|BIG-IP | | |applicable| | |BIG-IP |
|(Advanced +------+--------------+----------+Medium |5.9 |Advanced WAF |
|WAF, ASM) |13.x |None |Not | | |and ASM |
| | | |applicable| | | |
| +------+--------------+----------+ | | |
| |12.x |None |Not | | | |
| | | |applicable| | | |
| +------+--------------+----------+ | | |
| |11.x |None |Not | | | |
| | | |applicable| | | |
+------------+------+--------------+----------+----------+------+-------------+
| |16.x |None |Not | | | |
| | | |applicable| | | |
| +------+--------------+----------+ | | |
| |15.x |None |Not | | | |
| | | |applicable| | | |
| +------+--------------+----------+ | | |
| |14.x |None |Not | | | |
|BIG-IP (all | | |applicable|Not | | |
|other +------+--------------+----------+vulnerable|None |None |
|modules) |13.x |None |Not | | | |
| | | |applicable| | | |
| +------+--------------+----------+ | | |
| |12.x |None |Not | | | |
| | | |applicable| | | |
| +------+--------------+----------+ | | |
| |11.x |None |Not | | | |
| | | |applicable| | | |
+------------+------+--------------+----------+----------+------+-------------+
| |8.x |None |Not | | | |
| | | |applicable| | | |
|BIG-IQ +------+--------------+----------+ | | |
|Centralized |7.x |None |Not |Not |None |None |
|Management | | |applicable|vulnerable| | |
| +------+--------------+----------+ | | |
| |6.x |None |Not | | | |
| | | |applicable| | | |
+------------+------+--------------+----------+----------+------+-------------+
|F5OS |1.x |None |Not |Not |None |None |
| | | |applicable|vulnerable| | |
+------------+------+--------------+----------+----------+------+-------------+
|Traffix SDC |5.x |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.
^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 upgrading 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.
Mitigation
Configure systems with high availability (HA) clustering. For more information,
refer to K02234544: Manually setting up device service clustering.
Configure the HA table to take specific actions. For more information, refer to
K9231: Overview of BIG-IP daemon heartbeat failsafe.
Acknowledgements
This issue was discovered internally by F5.
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 software lifecycle policy
o K9502: BIG-IP hotfix and point release matrix
o K13123: Managing BIG-IP product hotfixes (11.x - 16.x)
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
- --------------------------------------------------------------------------------
K42051445: BIG-IP Advanced WAF and ASM WebSocket vulnerability CVE-2021-23030
Original Publication Date: 24 Aug, 2021
Security Advisory Description
When a WebSocket profile is configured on a virtual server, undisclosed
requests can cause bd to terminate. (CVE-2021-23030)
Impact
Traffic is disrupted while the bd process restarts. This vulnerability allows a
remote attacker to cause a denial-of-service (DoS) on the BIG-IP system. There
is no control plane exposure; this is a data plane issue only.
Security Advisory Status
F5 Product Development has assigned ID 980125 (BIG-IP) to this vulnerability.
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 table. For more
information about security advisory versioning, refer to K51812227:
Understanding security advisory versioning.
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. Additionally, software
versions preceding those listed in the following table have reached the End of
Technical Support (EoTS) phase of their lifecycle and are no longer evaluated
for security issues. For more information, refer to the Security hotfixes
section of K4602: Overview of the F5 security vulnerability response policy.
+-----------+------+-----------+----------+----------+------+-----------------+
| | |Versions |Fixes | |CVSSv3|Vulnerable |
|Product |Branch|known to be|introduced|Severity |score^|component or |
| | |vulnerable^|in | |2 |feature |
| | |1 | | | | |
+-----------+------+-----------+----------+----------+------+-----------------+
| |16.x |16.0.0 - |16.1.0 | | | |
| | |16.0.1 |16.0.1.2 | | | |
| +------+-----------+----------+ | | |
| |15.x |15.1.0 - |15.1.3.1 | | | |
| | |15.1.3 | | | | |
| +------+-----------+----------+ | | |
| |14.x |14.1.0 - |14.1.4.3 | | |BIG-IP Advanced |
|BIG-IP | |14.1.4 | | | |WAF and ASM |
|(Advanced +------+-----------+----------+High |7.5 |WebSocket |
|WAF, ASM) |13.x |13.1.0 - |13.1.4.1 | | |processing |
| | |13.1.4 | | | | |
| +------+-----------+----------+ | | |
| |12.x |12.1.0 - |Will not | | | |
| | |12.1.6 |fix | | | |
| +------+-----------+----------+ | | |
| |11.x |None |Not | | | |
| | | |applicable| | | |
+-----------+------+-----------+----------+----------+------+-----------------+
| |16.x |None |Not | | | |
| | | |applicable| | | |
| +------+-----------+----------+ | | |
| |15.x |None |Not | | | |
| | | |applicable| | | |
| +------+-----------+----------+ | | |
| |14.x |None |Not | | | |
|BIG-IP (all| | |applicable|Not | | |
|other +------+-----------+----------+vulnerable|None |None |
|modules) |13.x |None |Not | | | |
| | | |applicable| | | |
| +------+-----------+----------+ | | |
| |12.x |None |Not | | | |
| | | |applicable| | | |
| +------+-----------+----------+ | | |
| |11.x |None |Not | | | |
| | | |applicable| | | |
+-----------+------+-----------+----------+----------+------+-----------------+
| |8.x |None |Not | | | |
| | | |applicable| | | |
|BIG-IQ +------+-----------+----------+ | | |
|Centralized|7.x |None |Not |Not |None |None |
|Management | | |applicable|vulnerable| | |
| +------+-----------+----------+ | | |
| |6.x |None |Not | | | |
| | | |applicable| | | |
+-----------+------+-----------+----------+----------+------+-----------------+
|F5OS |1.x |None |Not |Not |None |None |
| | | |applicable|vulnerable| | |
+-----------+------+-----------+----------+----------+------+-----------------+
|Traffix SDC|5.x |None |Not |Not |None |None |
| | | |applicable|vulnerable| | |
+-----------+------+-----------+----------+----------+------+-----------------+
^1F5 only evaluates software versions that have not yet reached the End of
Technical Support (EoTS) phase of their lifecycle.
^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 upgrading to a version listed
in the Fixes introduced in column. If the table lists only an older version
than what you are currently running, or does not list a non-vulnerable version,
then no upgrade candidate currently exists.
Mitigation
o Configure systems with high availability (HA) clustering. For more
information, refer to K02234544: Manually setting up device service
clustering.
o Configure the HA table to take specific actions. For more information,
refer to K9231: Overview of BIG-IP daemon heartbeat failsafe.
Acknowledgements
This issue was discovered internally by F5.
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 software lifecycle policy
o K9502: BIG-IP hotfix and point release matrix
o K13123: Managing BIG-IP product hotfixes (11.x - 16.x)
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
- --------------------------------------------------------------------------------
K05314769: BIG-IP Advanced WAF and ASM WebSocket vulnerability CVE-2021-23033
Original Publication Date: 24 Aug, 2021
Security Advisory Description
When a WebSocket profile is configured on a virtual server, undisclosed
requests can cause bd to terminate. (CVE-2021-23033)
Impact
Traffic is disrupted while the bd process restarts. This vulnerability allows a
remote attacker to cause a denial-of-service (DoS) on the BIG-IP system. There
is no control plane exposure; this is a data plane issue only.
Security Advisory Status
F5 Product Development has assigned IDs 989361 and 989009 (BIG-IP) to this
vulnerability.
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 table. For more
information about security advisory versioning, refer to K51812227:
Understanding security advisory versioning.
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. Additionally, software
versions preceding those listed in the following table have reached the End of
Technical Support (EoTS) phase of their lifecycle and are no longer evaluated
for security issues. For more information, refer to the Security hotfixes
section of K4602: Overview of the F5 security vulnerability response policy.
+-----------+------+-----------+----------+----------+------+-----------------+
| | |Versions |Fixes | |CVSSv3|Vulnerable |
|Product |Branch|known to be|introduced|Severity |score^|component or |
| | |vulnerable^|in | |2 |feature |
| | |1 | | | | |
+-----------+------+-----------+----------+----------+------+-----------------+
| |16.x |16.0.0 - |16.1.0 | | | |
| | |16.0.1 | | | | |
| +------+-----------+----------+ | | |
| |15.x |15.1.0 - |15.1.3.1 | | | |
| | |15.1.3 | | | | |
| +------+-----------+----------+ | | |
| |14.x |14.1.0 - |14.1.4.3 | | |BIG-IP Advanced |
|BIG-IP | |14.1.4 | | | |WAF and ASM |
|(Advanced +------+-----------+----------+High |7.5 |WebSocket |
|WAF, ASM) |13.x |13.1.0 - |13.1.4.1 | | |processing |
| | |13.1.4 | | | | |
| +------+-----------+----------+ | | |
| |12.x |12.1.0 - |Will not | | | |
| | |12.1.6 |fix | | | |
| +------+-----------+----------+ | | |
| |11.x |None |Not | | | |
| | | |applicable| | | |
+-----------+------+-----------+----------+----------+------+-----------------+
| |16.x |None |Not | | | |
| | | |applicable| | | |
| +------+-----------+----------+ | | |
| |15.x |None |Not | | | |
| | | |applicable| | | |
| +------+-----------+----------+ | | |
| |14.x |None |Not | | | |
|BIG-IP (all| | |applicable|Not | | |
|other +------+-----------+----------+vulnerable|None |None |
|modules) |13.x |None |Not | | | |
| | | |applicable| | | |
| +------+-----------+----------+ | | |
| |12.x |None |Not | | | |
| | | |applicable| | | |
| +------+-----------+----------+ | | |
| |11.x |None |Not | | | |
| | | |applicable| | | |
+-----------+------+-----------+----------+----------+------+-----------------+
| |8.x |None |Not | | | |
| | | |applicable| | | |
|BIG-IQ +------+-----------+----------+ | | |
|Centralized|7.x |None |Not |Not |None |None |
|Management | | |applicable|vulnerable| | |
| +------+-----------+----------+ | | |
| |6.x |None |Not | | | |
| | | |applicable| | | |
+-----------+------+-----------+----------+----------+------+-----------------+
|F5OS |1.x |None |Not |Not |None |None |
| | | |applicable|vulnerable| | |
+-----------+------+-----------+----------+----------+------+-----------------+
|Traffix SDC|5.x |None |Not |Not |None |None |
| | | |applicable|vulnerable| | |
+-----------+------+-----------+----------+----------+------+-----------------+
^1F5 only evaluates software versions that have not yet reached the End of
Technical Support (EoTS) phase of their lifecycle.
^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 upgrading 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.
Mitigation
o Configure systems with high availability (HA) clustering. For more
information, refer to K02234544: Manually setting up device service
clustering.
o Configure the HA table to take specific actions. For more information,
refer to K9231: Overview of BIG-IP daemon heartbeat failsafe.
Acknowledgements
This issue was discovered internally by F5.
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 software lifecycle policy
o K9502: BIG-IP hotfix and point release matrix
o K13123: Managing BIG-IP product hotfixes (11.x - 16.x)
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
- --------------------------------------------------------------------------------
K41351250: BIG-IP Advanced WAF and BIG-IP ASM vulnerability CVE-2021-23031
Original Publication Date: 13 Aug, 2021
Latest Publication Date: 24 Aug, 2021
Security Advisory Description
An authenticated user may perform a privilege escalation on BIG-IP Advanced WAF
and ASM TMUI. (CVE-2021-23031)
Impact
When this vulnerability is exploited, an authenticated attacker with access to
the Configuration utility can execute arbitrary system commands, create or
delete files, and/or disable services. This vulnerability may result in
complete system compromise.
Security Advisory Status
F5 Product Development has assigned ID 980809 (BIG-IP) to this vulnerability.
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 table. For more
information about security advisory versioning, refer to K51812227:
Understanding security advisory versioning.
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. Additionally, software
versions preceding those listed in the following table have reached the End of
Technical Support (EoTS) phase of their lifecycle and are no longer evaluated
for security issues. For more information, refer to the Security hotfixes
section of K4602: Overview of the F5 security vulnerability response policy.
+-----------+------+-------------+----------+------------+------+-------------+
| | |Versions |Fixes | |CVSSv3|Vulnerable |
|Product |Branch|known to be |introduced|Severity |score^|component or |
| | |vulnerable^1 |in | |2 |feature |
+-----------+------+-------------+----------+------------+------+-------------+
| |16.x |16.0.0 - |16.1.0 | | | |
| | |16.0.1 |16.0.1.2 | | | |
| +------+-------------+----------+ | | |
| |15.x |15.1.0 - |15.1.3 | | | |
| | |15.1.2 | | | | |
| +------+-------------+----------+High | | |
|BIG-IP |14.x |14.1.0 - |14.1.4.1 | |8.8 | |
|(Advanced | |14.1.4 | |-- | |TMUI/ |
|WAF and +------+-------------+----------+ |-- |Configuration|
|ASM) |13.x |13.1.0 - |13.1.4 |Critical - | |utility |
| | |13.1.3 | |Appliance |9.9^3 | |
| +------+-------------+----------+mode only^3 | | |
| |12.x |12.1.0 - |12.1.6 | | | |
| | |12.1.5 | | | | |
| +------+-------------+----------+ | | |
| |11.x |11.6.1 - |11.6.5.3 | | | |
| | |11.6.5 | | | | |
+-----------+------+-------------+----------+------------+------+-------------+
| |16.x |None |Not | | | |
| | | |applicable| | | |
| +------+-------------+----------+ | | |
| |15.x |None |Not | | | |
| | | |applicable| | | |
| +------+-------------+----------+ | | |
| |14.x |None |Not | | | |
|BIG-IP (all| | |applicable|Not | | |
|other +------+-------------+----------+vulnerable |None |None |
|modules) |13.x |None |Not | | | |
| | | |applicable| | | |
| +------+-------------+----------+ | | |
| |12.x |None |Not | | | |
| | | |applicable| | | |
| +------+-------------+----------+ | | |
| |11.x |None |Not | | | |
| | | |applicable| | | |
+-----------+------+-------------+----------+------------+------+-------------+
| |8.x |None |Not | | | |
| | | |applicable| | | |
|BIG-IQ +------+-------------+----------+ | | |
|Centralized|7.x |None |Not |Not |None |None |
|Management | | |applicable|vulnerable^4| | |
| +------+-------------+----------+ | | |
| |6.x |None |Not | | | |
| | | |applicable| | | |
+-----------+------+-------------+----------+------------+------+-------------+
|F5OS |1.x |None |Not |Not |None |None |
| | | |applicable|vulnerable | | |
+-----------+------+-------------+----------+------------+------+-------------+
|Traffix SDC|5.x |None |Not |Not |None |None |
| | | |applicable|vulnerable | | |
+-----------+------+-------------+----------+------------+------+-------------+
^1F5 only evaluates software versions that have not yet reached the End of
Technical Support (EoTS) phase of their lifecycle.
^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.
^3The limited number of customers using Appliance mode have Scope: Changed,
which raises the CVSSv3 score to 9.9. For information about Appliance mode,
refer to K12815: Overview of Appliance mode.
^4The specified products contain the affected code. However, F5 identifies the
vulnerability status as Not vulnerable because the attacker cannot exploit the
code in default, standard, or recommended configurations.
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 upgrading 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.
Mitigation
As this attack is conducted by legitimate, authenticated users, there is no
viable mitigation that also allows users access to the Configuration utility.
The only mitigation is to remove access for users who are not completely
trusted.
Until it is possible to install a fixed version, you can use the
following temporary mitigations. These mitigations restrict access to the
Configuration utility to only trusted networks or devices, thereby limiting the
attack surface.
o Block Configuration utility access through self IP addresses
o Block Configuration utility access through the management interface
Block Configuration utility access through self IP addresses
You can block all access to the Configuration utility 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 the
Configuration utility. By default, the Configuration utility listens on TCP
port 443. If you modified the default port, ensure that you block 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 - 16.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: Configuring CIDR Network Addresses for the BIG-IP packet filter
Block Configuration utility access through the management interface
To mitigate this vulnerability for affected F5 products, restrict management
access to F5 products 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 K13309: Restricting access to the Configuration utility by source IP
address (11.x - 16.x)
o K13092: Overview of securing access to the BIG-IP system
o K46122561: Restricting access to the management interface using network
firewall rules
Acknowledgements
This issue was discovered internally by F5.
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 software lifecycle policy
o K9502: BIG-IP hotfix and point release matrix
o K13123: Managing BIG-IP product hotfixes (11.x - 16.x)
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
- --------------------------------------------------------------------------------
K05391775: The BIG-IP ASM system may not properly perform attack signature
checks
Original Publication Date: 24 Aug, 2021
Security Advisory Description
The BIG-IP ASM system may not properly perform attack signature checks on
request and response content.
This issue occurs when all of the following conditions are met:
o A security policy is enabled with attack signatures that check the full
content of the request and response.
o An undisclosed element of the request or response is missing.
Impact
Back-end servers behind a web application firewall (WAF) deployed by BIG-IP ASM
or F5 Advanced WAF are exposed to certain application attacks due to request
and response content not matching attack signatures.
Symptoms
As a result of this issue, you may encounter the following symptom:
o Some content attack signatures do not match an HTTP request with malicious
content, and the system forwards the request to the back-end servers
without logging a violation.
Security Advisory Status
F5 Product Development has assigned ID 987157 to this issue. F5 has confirmed
that this issue exists in the products listed in the Applies to (see versions)
box, located in the upper-right corner of this article. For information about
releases, point releases, or hotfixes that resolve this issue, refer to the
following table.
Note: F5 only evaluates 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.
+--------------------+-------------------+----------------+
|Type of fix |Fixes introduced in|Related articles|
+--------------------+-------------------+----------------+
|Release |None |None |
+--------------------+-------------------+----------------+
|Point release/hotfix|None |None |
+--------------------+-------------------+----------------+
Recommended Actions
Workaround
There is no workaround for this issue.
Supplemental Information
o K4602: Overview of the F5 security vulnerability response policy
o K4918: Overview of the F5 critical issue hotfix policy
o K8986: F5 software lifecycle policy
o K9502: BIG-IP hotfix and point release matrix
o K13123: Managing BIG-IP product hotfixes (11.x - 16.x)
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
- --------------------------------------------------------------------------------
K30150004: The Advanced WAF and BIG-IP ASM attack signature check may fail to
detect and block malicious requests
Original Publication Date: 24 Aug, 2021
Security Advisory Description
The F5 Advanced Web Application Firewall (WAF) and BIG-IP ASM attack signature
check may fail to detect and block malicious request containing certain
decimal-coded characters.
Impact
The attack signature check fails to detect and block malicious HTTP requests as
expected.
Symptoms
As a result of this issue, the Advanced WAF/BIG-IP ASM system does not block
some requests.
Security Advisory Status
F5 Product Development has assigned ID 943913 to this issue. F5 has confirmed
that this issue exists in the products listed in the Applies to (see versions)
box, located in the upper-right corner of this article. For information about
releases, point releases, or hotfixes that resolve this issue, refer to the
following table.
Note: F5 only evaluates software versions that have not yet reached the End of
Technical Support (EoTS) phase of their lifecycle.
+------------------+-----------------+----------------------------------------+
|Type of fix |Fixes introduced |Related articles |
| |in | |
+------------------+-----------------+----------------------------------------+
|Release |16.1.0 |K2200: Most recent versions of F5 |
| | |software |
+------------------+-----------------+----------------------------------------+
| |16.0.1.2 | |
|Point release/ |15.1.3.1 |K9502: BIG-IP hotfix and point release |
|hotfix |14.1.4.2 |matrix |
| |13.1.4.1 | |
+------------------+-----------------+----------------------------------------+
Recommended Actions
Workaround
There is no workaround for this issue.
Supplemental Information
o K51812227: Understanding security advisory versioning
o K41942608: Overview of AskF5 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 software lifecycle policy
o K9502: BIG-IP hotfix and point release matrix
o K13123: Managing BIG-IP product hotfixes (11.x - 16.x)
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 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: http://www.auscert.org.au/render.html?it=1967
iQIVAwUBYSWWAeNLKJtyKPYoAQg3Xg//fIWp1ZETfptFRPnaMNYx2PFIf5KYOEij
JWuamfJSFwqnMoCZpURTx0xGfBmb//lHVohc/SeiNkgZLBTGeUKUJ81NKKX4W26G
NRgBk7FrDzfojypOzodFXX2op8jvB7dD4djd/URApz3m+ymg6iAxJ+V4ayqKaGvi
K/7soWVBSxuNjAECOBLirZF46EILshdaQxPyB5s5iRWaQXcTyhQ3eBjVd3YqqTY8
YokKFt1wBPKCSxIeoMkr90QDLWGxJiuvGwJhiiH0tQvH9Pdj2X6yNYMpZBYsGfyk
E9FYc9dJNLbRAGajdtyR8987BaDw806RiGU3AUOKOOzqQq7S5D2ErDHNviP2dvrA
pIIo31Ps8P+mhM8NUCSHR1VWE50jk1INH/PFBHIe1LidI1sRM8uJ6LTvPv3wuR4Y
nX+Y/gdmHNazkHg8/lfhrq7jO7NpxBoAB42LaWXIYMcKi7n5ncrcw7XH7691avJs
2Porr8lGYb8hosiktyQVOwKsnrtcrTISbcMBRfCmqzeoxrngudX0U6NVpn1bNimq
mSTaZ86zPatsBtbgT+j/aLsO8cwsvrOdwUpgeKO+kAQZJZEFDxSVBYuWMyzFCMDm
yABjgrmKmcYli95uLMNln7tpriLeNlFaVXBpXu9vGwNDKjNfSiGgCQhrq/b1p8nQ
WYBSNGXlnag=
=hF78
-----END PGP SIGNATURE-----