Protect yourself against future threats.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
===========================================================================
AUSCERT External Security Bulletin Redistribution
ESB-2021.1451
BIG-IP ASM and Advanced WAF WebSocket vulnerability CVE-2021-23010
29 April 2021
===========================================================================
AusCERT Security Bulletin Summary
---------------------------------
Product: BIG-IP (ASM)
Publisher: F5 Networks
Operating System: Network Appliance
Impact/Access: Denial of Service -- Remote/Unauthenticated
Resolution: Patch/Upgrade
CVE Names: CVE-2021-23010
Original Bulletin:
https://support.f5.com/csp/article/K18570111
- --------------------------BEGIN INCLUDED TEXT--------------------
K18570111: BIG-IP ASM and Advanced WAF WebSocket vulnerability CVE-2021-23010
Original Publication Date: 29 Apr, 2021
Security Advisory Description
When the BIG-IP ASM/Advanced WAF system processes WebSocket requests with JSON
payloads using the default JSON content profile in the ASM security policy, the
BIG-IP ASM bd process may produce a core file. (CVE-2021-23010)
Impact
When this vulnerability is exploited, the BIG-IP ASM bd process may produce a
core file, interrupt traffic processing, and cause a failover event.
Security Advisory Status
F5 Product Development has assigned ID 943125 (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.0.1.1 | | | |
| | |16.0.1 | | | | |
| +------+--------------+----------+ | | |
| |15.x |15.1.0 - |15.1.2 | | | |
| | |15.1.1 | | | | |
| +------+--------------+----------+ | | |
| |14.x |14.1.0 - |14.1.3.1 | | | |
|BIG-IP (ASM)| |14.1.3 | | | | |
| +------+--------------+----------+High |7.5 |bd process |
| |13.x |13.1.0 - |13.1.3.5 | | | |
| | |13.1.3 | | | | |
| +------+--------------+----------+ | | |
| |12.x |12.1.0 - |12.1.5.3 | | | |
| | |12.1.5 | | | | |
| +------+--------------+----------+ | | |
| |11.x |None |Not | | | |
| | | |applicable| | | |
+------------+------+--------------+----------+----------+------+-------------+
| |16.x |None |Not | | | |
| | | |applicable| | | |
| +------+--------------+----------+ | | |
| |15.x |None |Not | | | |
| | | |applicable| | | |
| +------+--------------+----------+ | | |
| |14.x |None |Not | | | |
|BIG-IP (all | | |applicable|Not | | |
|modules) +------+--------------+----------+vulnerable|None |None |
| |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
To mitigate this vulnerability, you can use the ASM Security menu to create a
new custom JSON content profile and then apply it to Allowed WebSocket URLs. To
do so, perform both of the following procedures:
o Create a new custom JSON content profile
o Apply the newly created JSON content profile to Allowed WebSocket URLs
Impact of actions: Performing the following procedures should not have a
negative impact on your system.
Create a new custom JSON content profile
1. Log in to the Configuration utility.
2. Go to Security > Application Security > Content Profiles > JSON Profiles.
3. Select Create.
4. Enter a unique profile name.
5. If required, configure any customized settings. Otherwise, you can use the
default settings.
6. Select Create.
Apply the newly created JSON content profile to Allowed WebSocket URLs
1. Log in to the Configuration utility.
2. Go to Security > Application Security > URLs > Allowed URLs > Allowed
WebSocket URLs.
3. Select the WebSocket URL.
4. Open the first WebSocket URL by selecting its name.
5. For Payload Enforcement, in the JSON Profile list, select the custom JSON
profile you created in the previous procedure.
6. Select Update.
7. Repeat steps 5 and 6 for every WebSocket URL listed.
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
- --------------------------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
iQIVAwUBYIoEduNLKJtyKPYoAQgdFg/+NOBDxXmVdNSLEilzT81jSQ79Q/KwFb3k
ItomxCcNPx30RESLdCDJl0kLYCe6iDrCbvZeZa4vuxsjBGbei6RzDRKyiKDN233g
n+yuq/bGj7fqHBqwcjW0ucbwOEXJTqWX9mkn4I00RT3ZGZvL1HouvOFW0yYe3BpL
gIrcbFCJAT+u0sLCv3X66pfUIIMWG0AtP2YOxuN7hhciQi4KTurF70nh1CtSVU76
B8u/CgFfYM8qkQbynqm3Vk1N1X5lzndrTtMizHazkyPaylSe4khuYtqiqHEXof1x
oj2yb3tOllouu55PlKGjtlRTcPrGI/gSyLNLX4y6gaZCfC5i/SdwZZzjBvwKXnBL
/Tpk4nN4bx5rBBoREvvV7iwRkwGd/8yrjKjGPCeZ3Cl7D2DXQBQcIc4xcguCsry+
rWX+u1EDHPy0D5PvLdT4lyvm2/rOxi8YqofLp7tjqLNNq21MYsW2xCtEstxDI692
sEKcT/GkbiuiK4nDzWQhRAnyJwaLT6ljE/4QimsT11jgpklXLH17fTIycoLoea3l
AguHywWq5DVuxVqUOeifQE/QOYZpmK2dk1jmIalvMURFxLJjR0lseWOBtj8O0luV
vVCM9Eh5v12QqPVy+lB7+zv3zFFT6OhTgTyBq2HjaSAQL5mMtXRxAl+gzZEXQ/QC
WOWICweiMW4=
=EmDi
-----END PGP SIGNATURE-----