# CVE-2014-3520: Missing authorization in n/a

> Authenticated trustees can access unauthorized projects via V2 API trust token requests, leading to data exposure and security bypass.

- **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:** Yes
- **Published:** 26 Oct 2014
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2014-3520, GHSA-mv96-4gm9-mjhw, UBUNTU-CVE-2014-3520

## What is CVE-2014-3520?

CVE-2014-3520 is a medium-severity missing authorization vulnerability in n/a, published on 26 Oct 2014. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

OpenStack Identity (Keystone) before 2013.2.4, 2014.x before 2014.1.2, and Juno before Juno-2 allows remote authenticated trustees to gain access to an unauthorized project for which the trustor has certain roles via the project ID in a V2 API trust token request.

Weakness: CWE-863 (Incorrect Authorization)

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

It affects 1 product.


Products: Openstack Keystone.

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

Upgrade to a fixed version.

## Is CVE-2014-3520 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-12690](https://insights.sbomify.com/CVE-2020-12690/): Insufficient Session Expiration in OpenStack Keystone (high 8.8)
- [CVE-2019-19687](https://insights.sbomify.com/CVE-2019-19687/): OpenStack Keystone Credential Leakage (high 8.8)
- [CVE-2026-43001](https://insights.sbomify.com/CVE-2026-43001/): OpenStack Keystone has an Incorrect Authorization Issue (high 7.9)
- [CVE-2014-2828](https://insights.sbomify.com/CVE-2014-2828/): OpenStack Identity (Keystone) DoS through V3 API authentication chaining (high 7.8)
- [CVE-2021-38155](https://insights.sbomify.com/CVE-2021-38155/): OpenStack Keystone allows information disclosure during account locking (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-3520 is a medium-severity missing authorization vulnerability in n/a, published on 26 Oct 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-3520 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-3520/ (Markdown: https://insights.sbomify.com/CVE-2014-3520/index.md)
```

## Sources

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

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