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

> Remote organization administrators can escalate privileges to superuser by creating unauthorized accounts in Ansible Tower.

- **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:** 4 Feb 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-mv5f-9r7g-hr97

## What is CVE-2015-1481?

CVE-2015-1481 is a medium-severity vulnerability in n/a, published on 4 Feb 2015. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Ansible Tower (aka Ansible UI) before 2.0.5 allows remote organization administrators to gain privileges by creating a superuser account.

Weakness: CWE-264

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

It affects 1 product.


Products: Ansible Tower.

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

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

## Is CVE-2015-1481 being exploited?

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

Public exploit code:

- Ansible Tower 2.0.2 - Multiple Vulnerabilities (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2015-1482](https://insights.sbomify.com/CVE-2015-1482/): Auth bypass in n/a (medium 5.0)
- [CVE-2015-1368](https://insights.sbomify.com/CVE-2015-1368/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-1481 and fix it if it is affected.

What it is: CVE-2015-1481 is a medium-severity vulnerability in n/a, published on 4 Feb 2015. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-1481 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-2015-1481/ (Markdown: https://insights.sbomify.com/CVE-2015-1481/index.md)
```

## Sources

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

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