# CVE-2018-5511: Command injection in BIG-IP (LTM, AAM, AFM, Analytics, APM, ASM, DNS, Edge Gateway, GTM, Link Controller, PEM, WebAccelerator, WebSafe)

> Authenticated administrators can bypass command restrictions in the BIG-IP Configuration utility to execute arbitrary commands.

- **Severity:** High 7.2 (`CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Apr 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-4cq3-3qxv-x93w

## What is CVE-2018-5511?

CVE-2018-5511 is a high-severity command injection vulnerability in F5 Big-Ip Access Policy Manager, published on 13 Apr 2018. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

On F5 BIG-IP 13.1.0-13.1.0.3 or 13.0.0, when authenticated administrative users execute commands in the Traffic Management User Interface (TMUI), also referred to as the BIG-IP Configuration utility, restrictions on allowed commands may not be enforced.

Weakness: CWE-470 (Use of Externally-Controlled Input to Select Classes or Code)

## Which versions are affected by CVE-2018-5511?

It affects 16 products.


Products: F5 Big-Ip Access Policy Manager, F5 Big-Ip Advanced Firewall Manager, F5 Big-Ip Analytics, F5 Big-Ip Application Acceleration Manager, F5 Big-Ip Application Security Manager, F5 Big-Ip Domain Name System, F5 Big-Ip Edge Gateway, F5 Big-Ip Enterprise Manager, F5 Big-Ip Global Traffic Manager, F5 Big-Ip Link Controller, F5 Big-Ip Local Traffic Manager, F5 Big-Ip Policy Enforcement Manager, F5 Big-Ip Webaccelerator, F5 Big-Ip Websafe, Vmware Workstation, Vmware Workstation Player.

## How do I fix CVE-2018-5511?

No fix has been published for CVE-2018-5511 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-5511 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-5511 exists.

Public exploit code:

- VMware Workstation 14.1.5 / VMware Player 15.0.2 - Host VMX Process Impersonation Hijack Privilege Escalation (exploitdb)

## Other vulnerabilities in F5 Big-Ip Access Policy Manager

- [CVE-2023-46747](https://insights.sbomify.com/CVE-2023-46747/): F5 BIG-IP Configuration Utility Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2022-1388](https://insights.sbomify.com/CVE-2022-1388/): F5 BIG-IP Missing Authentication (critical 9.8, exploited in the wild)
- [CVE-2021-22986](https://insights.sbomify.com/CVE-2021-22986/): F5 BIG-IP and BIG-IQ Centralized Management iControl REST Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2021-22991](https://insights.sbomify.com/CVE-2021-22991/): F5 BIG-IP Traffic Management Microkernel Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2020-5902](https://insights.sbomify.com/CVE-2020-5902/): F5 BIG-IP Traffic Management User Interface (TMUI) Remote Code Execution (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-5511 and fix it if it is affected.

What it is: CVE-2018-5511 is a high-severity command injection vulnerability in F5 Big-Ip Access Policy Manager, published on 13 Apr 2018. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-5511 exists.

Affected product: F5 Big-Ip Access Policy Manager. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-5511/ (Markdown: https://insights.sbomify.com/CVE-2018-5511/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-5511
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-5511
- OSV: https://osv.dev/vulnerability/CVE-2018-5511

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-5511/
Summaries are generated and may contain mistakes; the official description above is the record.