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

> Authenticated Resource Administrators can escalate privileges via iCall scripts in SOAP requests to the iControl API.

- **Severity:** Critical 9.0 (`AV:N/AC:L/Au:S/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Dec 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-fv4r-7842-6m86

## What is CVE-2015-3628?

CVE-2015-3628 is a critical vulnerability in F5 Big-Ip Access Policy Manager, published on 7 Dec 2015. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The iControl API in F5 BIG-IP LTM, AFM, Analytics, APM, ASM, Link Controller, and PEM 11.3.0 before 11.5.3 HF2 and 11.6.0 before 11.6.0 HF6, BIG-IP AAM 11.4.0 before 11.5.3 HF2 and 11.6.0 before 11.6.0 HF6, BIG-IP Edge Gateway, WebAccelerator, and WOM 11.3.0, BIG-IP GTM 11.3.0 before 11.6.0 HF6, BIG-IP PSM 11.3.0 through 11.4.1, Enterprise Manager 3.1.0 through 3.1.1, BIG-IQ Cloud and Security 4.0.0 through 4.5.0, BIG-IQ Device 4.2.0 through 4.5.0, and BIG-IQ ADC 4.5.0 allows remote authenticated users with the "Resource Administrator" role to gain privileges via an iCall (1) script or (2) handler in a SOAP request to iControl/iControlPortal.cgi.

Weakness: CWE-264

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

It affects 18 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 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 Protocol Security Module, F5 Big-Ip Wan Optimization Manager, F5 Big-Ip Webaccelerator, F5 Big-Iq Adc, F5 Big-Iq Cloud, F5 Big-Iq Device, F5 Big-Iq Security.

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

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

## Is CVE-2015-3628 being exploited?

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

Public exploit code:

- F5 iControl iCall::Script Root Command Execution (metasploit)
- F5 iControl - 'iCall::Script' Root 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-2015-3628 and fix it if it is affected.

What it is: CVE-2015-3628 is a critical vulnerability in F5 Big-Ip Access Policy Manager, published on 7 Dec 2015. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2015-3628 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-2015-3628/ (Markdown: https://insights.sbomify.com/CVE-2015-3628/index.md)
```

## Sources

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

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