# CVE-2014-9000: Privilege escalation in n/a

> Authenticated users can escalate privileges to administrator and execute arbitrary code in Mule Enterprise Management Console via a crafted request.

- **Severity:** Medium 6.5 (`AV:N/AC:L/Au:S/C:P/I:P/A:P`)
- **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:** 20 Nov 2014
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-fcxw-jr7h-j53p

## What is CVE-2014-9000?

CVE-2014-9000 is a medium-severity vulnerability in n/a, published on 20 Nov 2014. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Mule Enterprise Management Console (MMC) does not properly restrict access to handler/securityService.rpc, which allows remote authenticated users to gain administrator privileges and execute arbitrary code via a crafted request that adds a new user.  NOTE: this issue was originally reported for ESB Runtime 3.5.1, but it originates in MMC.

Weakness: CWE-264

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

It affects 1 product.


Products: Mulesoft Mule Enterprise Management Console.

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

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

## Is CVE-2014-9000 being exploited?

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

Public exploit code:

- Mulesoft ESB Runtime 3.5.1 - Privilege Escalation (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-9000 and fix it if it is affected.

What it is: CVE-2014-9000 is a medium-severity vulnerability in n/a, published on 20 Nov 2014. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-9000 in the wild and no public exploit code.

Affected product: n/a. 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-9000/ (Markdown: https://insights.sbomify.com/CVE-2014-9000/index.md)
```

## Sources

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

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