Big-IP Automation Toolchain vulnerabilitiesAnd the versions its exploited flaws hit.
Big-IP Automation Toolchain is made by F5. We track 11 published vulnerabilities in it, across 35 versions. 2 of them are on the list of flaws known to be exploited, the newest added on 31 October 2023. If you run Big-IP Automation Toolchain, check your version against the exploited flaws below and patch those first.
The most recent Big-IP Automation Toolchain flaw added to the known-exploited list is CVE-2023-46747, on 31 October 2023. We keep watching the known-exploited list.
Which versions of Big-IP Automation Toolchain do the exploited flaws hit?
Each exploited flaw lists the versions it affects, as published by the vendor. Find your version, then patch.
- CVE-2023-46747Exploited list, 31 Oct 2023
F5 BIG-IP Configuration Utility Authentication Bypass Vulnerability
13.1.0 to 13.1.514.1.0 to 14.1.515.1.0 to 15.1.1016.1.0 to 16.1.417.1.0 to 17.1.1 - CVE-2023-46748Exploited list, 31 Oct 2023
F5 BIG-IP Configuration Utility SQL Injection Vulnerability
13.1.0 to 13.1.514.1.0 to 14.1.515.1.0 to 15.1.1016.1.0 to 16.1.417.1.0 to 17.1.1
Which Big-IP Automation Toolchain vulnerabilities are being exploited?
2 flaws are on the government list of vulnerabilities known to be exploited. These are the ones criminals are using now, so they go first, whatever their severity score says.
- 9.8F5 BIG-IP Configuration Utility Authentication Bypass Vulnerability
F5 BIG-IP Configuration utility contains an authentication bypass using an alternate path or channel vulnerability due to undisclosed requests that may allow an unauthenticated attacker with network access to the...
- 8.8F5 BIG-IP Configuration Utility SQL Injection Vulnerability
F5 BIG-IP Configuration utility contains an SQL injection vulnerability that may allow an authenticated attacker with network access through the BIG-IP management port and/or self IP addresses to execute system commands.
Which Big-IP Automation Toolchain flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 97%
Undisclosed requests may bypass configuration utility authentication, allowing an attacker with network access to the BIG-IP system through the management port and/or self IP addresses to execute arbitrary system...
- 4.2%
An authenticated SQL injection vulnerability exists in the BIG-IP Configuration utility which may allow an authenticated attacker with network access to the Configuration utility through the BIG-IP management port...
- 0.5%CVE-2024-41727High
In BIG-IP tenants running on r2000 and r4000 series hardware, or BIG-IP Virtual Edition (VEs) using Intel E810 SR-IOV NIC, undisclosed traffic can cause an increase in memory resource utilization.
- 0.5%CVE-2024-39778High
When a stateless virtual server is configured on BIG-IP system with a High-Speed Bridge (HSB), undisclosed requests can cause TMM to terminate.
- 0.4%CVE-2024-41164High
When TCP profile with Multipath TCP enabled (MPTCP) is configured on a Virtual Server, undisclosed traffic along with conditions beyond the attackers control can cause TMM to terminate.
- 0.4%CVE-2025-61958High
A vulnerability exists in the iHealth command that may allow an authenticated attacker with at least a resource administrator role to bypass tmsh restrictions and gain access to a bash shell.
- 0.3%CVE-2025-59781High
When DNS cache is configured on a BIG-IP or BIG-IP Next CNF virtual server, undisclosed DNS queries can cause an increase in memory resource utilization.
- 0.3%CVE-2024-41723Medium
Undisclosed requests to BIG-IP iControl REST can lead to information leak of user account names.
- 0.2%
On BIG-IP systems, undisclosed traffic can cause data corruption and unauthorized data modification in protocols which do not have message integrity protection.
- 0.2%CVE-2025-61951High
Undisclosed traffic can cause the Traffic Management Microkernel (TMM) to terminate.
Running Big-IP Automation Toolchain? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 flaw being exploited affects software Acme tracks
F5 BIG-IP Configuration utility contains an authentication bypass using an alternate path or channel vulnerability due to undisclosed requests that may allow an unauthenticated attacker with network access to the BIG-IP system through the management port and/or self IP addresses to execute system commands. This vulnerability can be used in conjunction with CVE-2023-46748.
- Matched to
- Big-IP Automation Toolchain on Acme's software list
- What to do
- Patch first, then check for signs of use
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 11 published vulnerabilities listed under the name Big-IP Automation Toolchain, across 35 versions. The most recent Big-IP Automation Toolchain flaw added to the known-exploited list is CVE-2023-46747, on 31 October 2023.
2 are on the list of flaws known to be exploited. The most recently added are CVE-2023-46747 and CVE-2023-46748.
Each flaw names its own versions, usually as ranges. The newest, CVE-2023-46747, affects 13.1.0 to 13.1.5, 14.1.0 to 14.1.5, 15.1.0 to 15.1.10, 16.1.0 to 16.1.4 and more. The versions for every exploited flaw are listed on this page.
Create a EdgeProtect account and track Big-IP Automation Toolchain. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.