-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

===========================================================================
             AUSCERT External Security Bulletin Redistribution

                               ESB-2024.0989
      K98606833 : BIG-IP and BIG-IQ scp vulnerability CVE-2024-21782
                             15 February 2024

===========================================================================

        AusCERT Security Bulletin Summary
        ---------------------------------

Product:           BIG-IP
                   BIG-IQ scp
Publisher:         F5 Networks
Operating System:  Network Appliance
Resolution:        Patch/Upgrade
CVE Names:         CVE-2024-21782 CVE-2020-5873 

Original Bulletin: 
   https://my.f5.com/manage/s/article/K98606833

Comment: CVSS (Max):  6.7 CVE-2024-21782 (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/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:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

- --------------------------BEGIN INCLUDED TEXT--------------------

K98606833: BIG-IP and BIG-IQ scp vulnerability CVE-2024-21782

Published Date: Feb 14, 2024

Security Advisory Description

BIG-IP or BIG-IQ Resource Administrators and Certificate Managers who have
access to the secure copy (scp) utility but do not have access to Advanced
Shell (bash) can execute arbitrary commands with a specially crafted command
string. This vulnerability is due to an incomplete fix for CVE-2020-5873. (
CVE-2024-21782)

Impact

A local authenticated user can run arbitrary commands to gain access to
restricted information, modify files, or cause a denial-of-service (DoS).

Security Advisory Status

F5 Product Development has assigned IDs 994801 and 1041577 (BIG-IP and BIG-IQ)
to this vulnerability. This issue has been classified as CWE-78: Improper
Neutralization of Special Elements used in an OS Command ('OS Command
Injection').

To determine if your product and version have been evaluated for this
vulnerability, refer to the Evaluated products box. To determine if your
release is known to be vulnerable, the components or features that are affected
by the vulnerability, and for information about releases, point releases, or
hotfixes that address the vulnerability, refer to the following tables. You can
also use iHealth to diagnose a vulnerability for BIG-IP and BIG-IQ systems. For
more information about using iHealth, refer to K27404821: Using F5 iHealth to
diagnose vulnerabilities. For more information about security advisory
versioning, refer to K51812227: Understanding security advisory versioning.

In this section

  o BIG-IP Next
  o BIG-IP and BIG-IQ
  o F5 Distributed Cloud Services
  o F5OS
  o NGINX
  o Other products

BIG-IP Next

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 20.0.2, the fix also applies to 20.0.3, and all later
20.1.x releases. For more information, refer to K51812227: Understanding
security advisory versioning.

+------------+------+--------------+----------+----------+------+-------------+
|            |      |Versions known|Fixes     |          |CVSSv3|Vulnerable   |
|Product     |Branch|to be         |introduced|Severity  |score |component or |
|            |      |vulnerable^1  |in        |          |      |feature      |
+------------+------+--------------+----------+----------+------+-------------+
|BIG-IP Next |      |              |Not       |Not       |      |             |
|(all        |All   |None          |applicable|vulnerable|None  |None         |
|modules)    |      |              |          |          |      |             |
+------------+------+--------------+----------+----------+------+-------------+
|BIG-IP Next |      |              |Not       |Not       |      |             |
|Central     |All   |None          |applicable|vulnerable|None  |None         |
|Manager     |      |              |          |          |      |             |
+------------+------+--------------+----------+----------+------+-------------+
|BIG-IP Next |All   |None          |Not       |Not       |None  |None         |
|SPK         |      |              |applicable|vulnerable|      |             |
+------------+------+--------------+----------+----------+------+-------------+
|BIG-IP Next |All   |None          |Not       |Not       |None  |None         |
|CNF         |      |              |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.

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 16.1.2.1, the fix also applies to 16.1.2.2, and all
later 16.1.x releases (16.1.3.x, 16.1.4.x.). For more information, refer to
K51812227: Understanding security advisory versioning.

+-----------+------+-----------+---------------------------------+--------+------+----------+
|           |      |Versions   |                                 |        |CVSSv3|Vulnerable|
|Product    |Branch|known to be|Fixes introduced in              |Severity|score^|component |
|           |      |vulnerable^|                                 |        |2     |or feature|
|           |      |1          |                                 |        |      |          |
+-----------+------+-----------+---------------------------------+--------+------+----------+
|           |17.x  |17.1.0     |17.1.1                           |        |      |          |
|           +------+-----------+---------------------------------+        |      |          |
|BIG-IP (all|16.x  |16.1.0 -   |16.1.4                           |        |      |          |
|modules)   |      |16.1.3     |                                 |Medium  |6.7   |scp       |
|           +------+-----------+---------------------------------+        |      |          |
|           |15.x  |15.1.0 -   |15.1.9                           |        |      |          |
|           |      |15.1.8     |                                 |        |      |          |
+-----------+------+-----------+---------------------------------+--------+------+----------+
|BIG-IQ     |      |8.0.0 -    |8.3.0 +                          |        |      |          |
|Centralized|8.x   |8.3.0      |Hotfix-BIG-IQ-8.3.0.0.16.118-ENG^|Medium  |6.7   |scp       |
|Management |      |           |3                                |        |      |          |
+-----------+------+-----------+---------------------------------+--------+------+----------+

^1F5 evaluates only software versions that have not yet reached the End of
Technical Support (EoTS) phase of their lifecycle. For more information, refer
to the Security hotfixes section of K4602: Overview of the F5 security
vulnerability response policy.

^2The CVSSv3 score link takes you to a resource outside of MyF5, and it is
possible that the document may be removed without our knowledge.

^3F5 has fixed this issue in an engineering hotfix that is available for
versions of the BIG-IQ system which have not yet reached End of Software
Development. Customers affected by this issue can download the engineering
hotfix from the MyF5 Downloads page. For more information, refer to K000090258:
Download F5 products from MyF5. While F5 endeavors to release the most stable
code possible, engineering hotfixes do not undergo the extensive QA assessment
of scheduled software releases. F5 offers engineering hotfixes with no warranty
or guarantee of usability. For more information about the hotfix policy, refer
to K4918: Overview of the F5 critical issue hotfix policy.

F5 Distributed Cloud Services

+----------------------------+-----------+----------+-------------------------+
|Service                     |Severity   |CVSSv3    |Vulnerable component or  |
|                            |           |score     |feature                  |
+----------------------------+-----------+----------+-------------------------+
|F5 Distributed Cloud (all   |Not        |None      |None                     |
|services)                   |vulnerable |          |                         |
+----------------------------+-----------+----------+-------------------------+
|F5 Silverline (all services)|Not        |None      |None                     |
|                            |vulnerable |          |                         |
+----------------------------+-----------+----------+-------------------------+

F5OS

+-------+------+-----------------+----------+----------+------+---------------+
|       |      |Versions known to|Fixes     |          |CVSSv3|Vulnerable     |
|Product|Branch|be vulnerable^1  |introduced|Severity  |score |component or   |
|       |      |                 |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.

NGINX

+---------+------+---------------+----------+----------+------+---------------+
|         |      |Versions known |Fixes     |          |CVSSv3|Vulnerable     |
|Product  |Branch|to be          |introduced|Severity  |score |component or   |
|         |      |vulnerable^1   |in        |          |      |feature        |
+---------+------+---------------+----------+----------+------+---------------+
|NGINX    |      |               |Not       |Not       |      |               |
|(all     |All   |None           |applicable|vulnerable|None  |None           |
|products)|      |               |          |          |      |               |
+---------+------+---------------+----------+----------+------+---------------+

^1F5 evaluates only software versions that have not yet reached the End of
Technical Support (EoTS) phase of their lifecycle. For more information, refer
to the Security hotfixes section of K4602: Overview of the F5 security
vulnerability response policy.

Other products

+-------+------+-----------------+----------+----------+------+---------------+
|       |      |Versions known to|Fixes     |          |CVSSv3|Vulnerable     |
|Product|Branch|be vulnerable^1  |introduced|Severity  |score |component or   |
|       |      |                 |in        |          |      |feature        |
+-------+------+-----------------+----------+----------+------+---------------+
|Traffix|All   |None             |Not       |Not       |None  |None           |
|SDC    |      |                 |applicable|vulnerable|      |               |
+-------+------+-----------------+----------+----------+------+---------------+

^1F5 evaluates only software versions that have not yet reached the End of
Technical Support (EoTS) phase of their lifecycle. For more information, refer
to the Security hotfixes section of K4602: Overview of the F5 security
vulnerability response policy.

Security Advisory Recommended Actions

If you are running a version listed in the Versions known to be vulnerable
column, you can eliminate this vulnerability by installing a version listed in
the Fixes introduced in column. If the Fixes introduced in column does not list
a version for your branch, then no update candidate currently exists for that
branch and F5 recommends that you upgrade to a version with the fix (refer to
the tables).

If the Fixes introduced in column lists a version prior to the one you are
running, in the same branch, then your version should have the fix.

Mitigation

As this attack is conducted by legitimate, authenticated users, there is no
viable mitigation that also allows users access to the BIG-IP or BIG-IQ system.
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
BIG-IP or BIG-IQ command line through SSH to only trusted networks or devices,
thereby limiting the attack surface.

Note: The vulnerable component, the scp utility, relies on SSH.

  o Block SSH access through self IP addresses
  o Block SSH access through the management interface

Block SSH access through self IP addresses

You can block all access to the command line through SSH of your BIG-IP or
BIG-IQ system using self IP addresses. To do so, you can change the Port
Lockdown setting to Allow None for each self IP address on the system. If you
must open any ports, you should use the Allow Custom option, taking care to
block access to SSH. By default, the SSH service listens on TCP port 22.

Note: Performing this action prevents all access to SSH using the self IP
address. These changes may also impact other services.

Before you make changes to the configuration of your self IP addresses, F5
strongly recommends that you refer to the following articles:

  o K17333: Overview of port lockdown behavior (12.x - 17.x)
  o K39403510: Managing the port lockdown configuration on the BIG-IQ system
  o K13092: Overview of securing access to the BIG-IP system

If you must expose port 22 on your self IP addresses and want to restrict
access to specific IP ranges, you may consider using the packet filtering
functionality built into the BIG-IP system. For more information, refer to the
following article:

  o K13383: Configuring CIDR Network Addresses for the BIG-IP packet filter

For BIG-IQ self IP addresses where port 22 is exposed, use an external packet
filtering device such as BIG-IP AFM.

Block SSH access through the management interface

To mitigate this vulnerability for affected F5 products, you should restrict
management access to F5 products to only trusted users and devices over a
secure network. For more information about securing access to BIG-IP and BIG-IQ
systems, refer to the following articles:

  o K13092: Overview of securing access to the BIG-IP system
  o K46122561: Restrict access to the BIG-IP management interface using network
    firewall rules
  o K92748202: Restricting access to the BIG-IQ management interface using
    network firewall rules

Acknowledgments

This issue was discovered internally by F5.

Related Content

  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 K000090258: Download F5 products from MyF5
  o K9970: Subscribing to email notifications regarding F5 products
  o K9957: Creating a custom RSS feed to view new and updated documents
  o K000135931: Contact F5 Support

- --------------------------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/

iQIVAwUBZc1jQMkNZI30y1K9AQjGRw//VxsOZqcHeeQ26lJ2M9H2WoehjdF4/QBX
I0dT5Hf6KVSCdjUVYmlEGhf37vew+d2RO+TZaM1rpVjBr3vr8WATErs86b3f302S
ZJgrpTx3HC2F1IIZLWxZxb3/J2KfIGA/To1JL9fxZK3xafDpz3Juc94tLmnkjyt0
/llY+OzcciSUsOITS4lVHIDBmvTsL88vZ8X7LEN3CTRNkf/ej5/GnAgq1LolsdZP
R64tktUmWYKF4lERjoL64jX07cYPADrRKOYcQmLaa/uE0cX8/dbu+nJs2OiBbGHV
i+NHORlXvEhK9WWGdIfAU5N2noyut/mRxTNMCZBpOyXOwLK/3/RsznIdmTcH188D
0VpEOpb1xGYPpNYPh1EHDdkDjGiJj3VUJr4BV82nkL96dxlo5JT0R+r9Tw4NUh5/
VrDTkIW+G8v/ecRr3mEpKUQqTQtjceJNH43+JuAza8WAD57TopY1m7zSGdQsj6Q3
1d24J1tX1sXKP348JXiSLk5nBDoApbQ5CsAwpD9daZ0ILhbYryLRFBB1DjsWg7yi
wPt3F9AmMVzBzxETLglFZTPXxH9YUg6iA7BbwFpGRWpchD7ft0TtgDf3KAuP8cPN
rSc59E4wBHZtR51ZKim8x328t8gymGJNFdeaTWGRXkZcyxtacQdJwGsOVexCrY/y
ytkkiavnyqk=
=gJHr
-----END PGP SIGNATURE-----