my.f5.com Open in urlscan Pro
35.158.127.52  Public Scan

Form analysis
1 forms found in the DOM

POST

<form id="fileUploadForm" enctype="multipart/form-data" method="post" target="fileUploadIframe"><input type="file" id="fileSelector" name="file" style="display: none;"><input name="filename" type="hidden"></form>

Text Content

Loading
×Sorry to interrupt
CSS Error

Refresh
Skip to content
 * F5.com
 * DevCentral
 * Partners

 * MyF5

Home PageMyF5
Toggle showing sub menu for Support


Toggle showing sub menu for My Products & Plans


Toggle showing sub menu for Resources


Open navigation menuHome PageMyF5
Search
Sign In

Search...Search...

Search tips

Security Advisory


K000137365: BIG-IP CONFIGURATION UTILITY AUTHENTICATED SQL INJECTION
VULNERABILITY CVE-2023-46748

Published Date: Oct 26, 2023Updated Date: Dec 28, 2023
 * Download Article
 * Bookmark Article
 * Show social share buttons

AI Recommended Content
Toggle showing the products this article Evaluated products:

Security Advisory Description

An authenticated SQL injection vulnerability exists in the BIG-IP Configuration
utility. (CVE-2023-46748)

Impact

This vulnerability may allow an authenticated attacker with network access to
the Configuration utility through the BIG-IP management port and/or self IP
addresses to execute arbitrary system commands. There is no data plane exposure;
this is a control plane issue only.

Security Advisory Status

F5 Product Development has assigned ID 1381357 (BIG-IP) to this vulnerability.
This issue has been classified as CWE-89: Improper Neutralization of Special
Elements used in an SQL Command ('SQL 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

 * BIG-IP Next
 * BIG-IP and BIG-IQ
 * F5 Distributed Cloud Services
 * F5OS
 * NGINX
 * 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.

ProductBranchVersions known to be vulnerable1Fixes introduced inSeverityCVSSv3
scoreVulnerable component or feature

BIG-IP Next (all modules)

AllNoneNot applicableNot vulnerableNoneNoneBIG-IP Next Central ManagerAllNoneNot
applicableNot vulnerableNoneNoneBIG-IP Next SPKAllNoneNot applicableNot
vulnerableNoneNoneBIG-IP Next CNFAllNoneNot applicableNot vulnerableNoneNone

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

ProductBranchVersions known to be vulnerable1Fixes introduced inSeverityCVSSv3
score2Vulnerable component or featureBIG-IP (all modules)17.x17.1.0 -
17.1.117.1.1.1
17.1.1 + Hotfix-BIGIP-17.1.1.0.2.6-ENG3
17.1.0.3 + Hotfix-BIGIP-17.1.0.3.0.75.4-ENGHigh8.8Configuration
utility16.x16.1.0 - 16.1.416.1.4.2
16.1.4.1 + Hotfix-BIGIP-16.1.4.1.0.50.5-ENG315.x15.1.0 - 15.1.1015.1.10.3
15.1.10.2 + Hotfix-BIGIP-15.1.10.2.0.44.2-ENG314.x14.1.0 - 14.1.514.1.5.6 +
Hotfix-BIGIP-14.1.5.6.0.10.6-ENG313.x13.1.0 - 13.1.513.1.5.1 +
Hotfix-BIGIP-13.1.5.1.0.20.2-ENG3BIG-IQ Centralized ManagementAllNoneNot
applicableNot vulnerableNoneNone

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-IP 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. After selecting your product and version from the Downloads
page, scroll to the bottom of the page to locate the hotfix file. For example,
to download Hotfix-BIGIP-17.1.0.3.0.75.4-ENG, select 17.1.0.3, then scroll down
to select Hotfix-BIGIP-17.1.0.3.0.75.4-ENG.iso. 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

ServiceSeverityCVSSv3 scoreVulnerable component or featureF5 Distributed Cloud
(all services)Not vulnerableNoneNoneF5 Silverline (all services)Not
vulnerableNoneNone

F5OS

ProductBranchVersions known to be vulnerable1Fixes introduced inSeverityCVSSv3
scoreVulnerable component or featureF5OS-AAllNoneNot applicableNot
vulnerableNoneNoneF5OS-CAllNoneNot applicableNot vulnerableNoneNone

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

ProductBranchVersions known to be vulnerable1Fixes introduced inSeverityCVSSv3
scoreVulnerable component or featureNGINX (all products)AllNoneNot applicableNot
vulnerableNoneNone

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

ProductBranchVersions known to be vulnerable1Fixes introduced inSeverityCVSSv3
scoreVulnerable component or featureTraffix SDCAllNoneNot applicableNot
vulnerableNoneNone

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 Configuration utility.
The only mitigation is to remove access for users who are not completely
trusted.

Until you can 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.

 * Block Configuration utility access through self IP addresses
 * 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:

 * K17333: Overview of port lockdown behavior (12.x - 17.x)
 * K13092: Overview of securing access to the BIG-IP system
 * K31003634: The Configuration utility of the Single-NIC BIG-IP Virtual Edition
   now defaults to TCP port 8443
 * 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:

 * 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 to F5 products to only trusted users and devices over a secure
network. For more information about securing access to BIG-IP systems, refer to
the following articles:

 * K13309: Restricting access to the Configuration utility by source IP address
   (11.x - 17.x)
 * K13092: Overview of securing access to the BIG-IP system
 * K46122561: Restrict access to the management interface using network firewall
   rules

Indicators of compromise

Important: This section was last updated on October 30, 2023 at 14:35 Pacific
time.

This information is based on the evidence F5 has seen on compromised devices,
which appear to be reliable indicators. It is important to note that not all
exploited systems may show the same indicators, and, indeed, a skilled attacker
may be able to remove traces of their work. It is not possible to prove a device
has not been compromised; when there is any uncertainty, you should consider the
device compromised. For information about handling suspected compromised
systems, please review K11438344: Considerations and guidance when you suspect a
security compromise on a BIG-IP system.

All versions

F5 has observed threat actors using this vulnerability in combination with
CVE-2023-46747. Below are the indicators of compromise observed with
CVE-2023-46748.

You may see entries in the /var/log/tomcat/catalina.out file similar to the
following example:

{...}
java.sql.SQLException: Column not found: 0.
{...)
sh: no job control in this shell
sh-4.2$ <EXECUTED SHELL COMMAND>
sh-4.2$ exit.

In the previous example, note the following:

 * In the line of Column not found: 0, the 0 can be replaced with a different
   number.
 * In the line of <EXECUTED SHELL COMMAND>, the command will be replaced with a
   different command.

Acknowledgments

F5 acknowledges researchers who would like to remain anonymous for bringing this
issue to our attention and following the highest standards of coordinated
disclosure.


RELATED CONTENT

 * K41942608: Overview of MyF5 security advisory articles
 * K12201527: Overview of Quarterly Security Notifications
 * K51812227: Understanding security advisory versioning
 * K4602: Overview of the F5 security vulnerability response policy
 * K4918: Overview of the F5 critical issue hotfix policy
 * K39757430: F5 product and services lifecycle policy index
 * K9502: BIG-IP hotfix and point release matrix
 * K13123: Managing BIG-IP product hotfixes (11.x - 17.x)
 * K48955220: Installing an OPSWAT Endpoint Security update on BIG-IP APM
   systems (11.4.x and later)
 * K000090258: Download F5 products from MyF5
 * K9970: Subscribing to email notifications regarding F5 products
 * K9957: Creating a custom RSS feed to view new and updated documents
 * K44525501: Overview of BIG-IP data plane and control plane


AI RECOMMENDED CONTENT

 * Policy - K4309: F5 hardware product lifecycle support policy
 * Knowledge - K000135931: Contact F5 Support
 * Knowledge - K29900360: F5 certification | Exams and blueprints
 * Knowledge - K84473448: How to download and install Windows BIG-IP Edge Client
   without an installation package

Return to Top



Contact Support

Live chat:Agent Offline
Have a Question?
 * Support and Sales ›

Follow Us
 * 
 * 
 * 
 * 
 * 

About F5
 * Corporate Information
 * Newsroom
 * Investor Relations
 * Careers
 * Contact Information
 * Communication Preferences

Education
 * Training
 * Certification
 * LearnF5
 * Free Online Training

F5 Sites
 * F5.com
 * DevCentral
 * MyF5
 * Partner Central
 * F5 Labs

Support Tasks
 * Read Support Policies
 * Create Support Case
 * Leave Feedback [+]

 * About F5
    * Corporate Information
    * Newsroom
    * Investor Relations
    * Careers
    * Contact Information
    * Communication Preferences

 * Education
    * Training
    * Certification
    * LearnF5
    * Free Online Training

 * F5 Sites
    * F5.com
    * DevCentral
    * MyF5
    * Partner Central
    * F5 Labs

 * Support Tasks
    * Read Support Policies
    * Create Support Case
    * Leave Feedback [+]

©2024 F5, Inc. All rights reserved.

 * Policies
 * Privacy
 * Trademarks
 * California Privacy
 * Do Not Sell My Personal Information
 * MyF5 Terms of Use
 * Cookie Preferenze
   Opens in a modal window

Noi diamo valore alla tua privacy
To provide the best experience, we leverage third-party technologies to
personalize what you see, and to better understand what content is important to
you. View our informativa sulla privacy for details.
Customize Settings No thanks Count me in



Loading