# CVE-2015-7393: Privilege escalation in n/a

> Local users with shell access can escalate privileges on F5 BIG-IP and BIG-IQ systems, requiring a patch to mitigate.

- **Severity:** High 7.4 (`CVSS:3.0/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Jan 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-wvh6-8pmw-ccff

## What is CVE-2015-7393?

CVE-2015-7393 is a high-severity vulnerability in F5 Big-Ip Access Policy Manager, published on 12 Jan 2016. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

dcoep in BIG-IP LTM, Analytics, APM, ASM, and Link Controller 11.2.0 through 11.6.0 and 12.0.0 before 12.0.0 HF1, BIG-IP AAM 11.4.0 through 11.6.0 and 12.0.0 before 12.0.0 HF1, BIG-IP AFM and PEM 11.3.0 through 11.6.0 and 12.0.0 before 12.0.0 HF1, BIG-IP DNS 12.0.0 before 12.0.0 HF1, BIG-IP Edge Gateway, WebAccelerator, and WOM 11.2.0 through 11.3.0, BIG-IP GTM 11.2.0 through 11.6.0, BIG-IP PSM 11.2.0 through 11.4.1, Enterprise Manager 3.0.0 through 3.1.1, BIG-IQ Cloud 4.0.0 through 4.5.0, BIG-IQ Device 4.2.0 through 4.5.0, BIG-IQ Security 4.0.0 through 4.5.0, BIG-IQ ADC 4.5.0, BIG-IQ Centralized Management 4.6.0, and BIG-IQ Cloud and Orchestration 1.0.0 allows local users with advanced shell (bash) access to gain privileges via unspecified vectors.

## Which versions are affected by CVE-2015-7393?

It affects 20 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 Global Traffic Manager, F5 Big-Ip Global Traffic Manager11.2.0, F5 Big-Ip Local Traffic Manager, F5 Big-Ip Policy Enforcement Manager, F5 Big-Ip Protocol Security Module, F5 Big-Ip Wan Optimization Manager, F5 Big-Ip Webaccelerator, F5 Big-Iq Application Delivery Controller, F5 Big-Iq Centralized Management, F5 Big-Iq Cloud, F5 Big-Iq Cloud and Orchestration, F5 Big-Iq Device, F5 Big-Iq Security.

## How do I fix CVE-2015-7393?

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

## Is CVE-2015-7393 being exploited?

There is no known exploitation of CVE-2015-7393 in the wild and no public exploit code.

## 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-2015-7393 and fix it if it is affected.

What it is: CVE-2015-7393 is a high-severity vulnerability in F5 Big-Ip Access Policy Manager, published on 12 Jan 2016. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-7393 in the wild and no public exploit code.

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-2015-7393/ (Markdown: https://insights.sbomify.com/CVE-2015-7393/index.md)
```

## Sources

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

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