# CVE-2014-2928: Command injection in n/a

> Remote administrators can execute arbitrary commands on F5 BIG-IP devices via shell metacharacters in SOAP requests.

- **Severity:** High 7.1 (`AV:N/AC:H/Au:S/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 May 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-2ggw-q935-g2j9

## What is CVE-2014-2928?

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

### Official description

The iControl API in F5 BIG-IP LTM, APM, ASM, GTM, Link Controller, and PSM 10.0.0 through 10.2.4 and 11.0.0 through 11.5.1, BIG-IP AAM 11.4.0 through 11.5.1, BIG-IP AFM and PEM 11.3.0 through 11.5.1, BIG-IP Analytics 11.0.0 through 11.5.1, BIG-IP Edge Gateway, WebAccelerator, WOM 10.1.0 through 10.2.4 and 11.0.0 through 11.3.0, Enterprise Manager 2.1.0 through 2.3.0 and 3.0.0 through 3.1.1, and BIG-IQ Cloud, Device, and Security 4.0.0 through 4.3.0 allows remote administrators to execute arbitrary commands via shell metacharacters in the hostname element in a SOAP request.

## Which versions are affected by CVE-2014-2928?

It affects 9 products.


Products: F5 Big-Ip Access Policy Manager, F5 Big-Ip Application Security Manager, F5 Big-Ip Edge Gateway, F5 Big-Ip Global Traffic Manager, F5 Big-Ip Link Controller, F5 Big-Ip Local Traffic Manager, F5 Big-Ip Protocol Security Module, F5 Big-Ip Wan Optimization Manager, F5 Big-Ip Webaccelerator.

## How do I fix CVE-2014-2928?

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

## Is CVE-2014-2928 being exploited?

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

Public exploit code:

- F5 iControl Remote Root Command Execution (metasploit)
- F5 iControl - Remote Command Execution (Metasploit) (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-2014-2928 and fix it if it is affected.

What it is: CVE-2014-2928 is a high-severity command injection vulnerability in F5 Big-Ip Access Policy Manager, published on 12 May 2014. 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-2014-2928 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-2014-2928/ (Markdown: https://insights.sbomify.com/CVE-2014-2928/index.md)
```

## Sources

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

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