# CVE-2012-3426: OpenStack Keystone token expiration issues

> Authenticated users can bypass authorization restrictions and maintain access via token chaining or stale tokens in OpenStack Keystone.

- **Severity:** Medium 4.9 (`AV:N/AC:M/Au:S/C:P/I:P/A:N`)
- **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:** 31 Jul 2012
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2012-3426, GHSA-xp97-6w7r-4cjc

## What is CVE-2012-3426?

CVE-2012-3426 is a medium-severity authentication bypass vulnerability in n/a, published on 31 Jul 2012. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

OpenStack Keystone before 2012.1.1, as used in OpenStack Folsom before Folsom-1 and OpenStack Essex, does not properly implement token expiration, which allows remote authenticated users to bypass intended authorization restrictions by (1) creating new tokens through token chaining, (2) leveraging possession of a token for a disabled user account, or (3) leveraging possession of a token for an account with a changed password.

Weakness: CWE-264

## Which versions are affected by CVE-2012-3426?

2 open source packages ship an affected version, including Keystone and keystone. It affects 3 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `Keystone` | PyPI | All versions | 8.0.0a0 |
| `keystone` | PyPI | All versions | 8.0.0a0 |

Products: Openstack Essex, Openstack Horizon, Openstack Keystone.

## How do I fix CVE-2012-3426?

Upgrade Keystone to 8.0.0a0 or later.

## Is CVE-2012-3426 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-0261](https://insights.sbomify.com/CVE-2013-0261/): Packstack: packstack: arbitrary file overwrite via symlink attack (high 8.8)
- [CVE-2013-0266](https://insights.sbomify.com/CVE-2013-0266/): Information disclosure in Red Hat Enterprise Linux OpenStack Platform 5 (Icehouse) (medium 5.5)
- [CVE-2012-4573](https://insights.sbomify.com/CVE-2012-4573/): OpenStack Glance arbitrary deletion of non-protected images (medium 5.5)
- [CVE-2012-5482](https://insights.sbomify.com/CVE-2012-5482/): OpenStack Glance arbitrary deletion of non-protected images (medium 5.5)
- [CVE-2012-3360](https://insights.sbomify.com/CVE-2012-3360/): OpenStack Nova Directory traversal vulnerability (medium 5.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-3426 and fix it if it is affected.

What it is: CVE-2012-3426 is a medium-severity authentication bypass vulnerability in n/a, published on 31 Jul 2012. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2012-3426 in the wild and no public exploit code.

Affected packages and fixed versions:
- Keystone (PyPI): affected all versions; fixed in 8.0.0a0
- keystone (PyPI): affected all versions; fixed in 8.0.0a0

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

## Sources

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

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