# CVE-2012-5563: OpenStack Keystone Insufficient token expiration

> Authenticated users can bypass authorization restrictions by chaining expired tokens to create new valid ones in OpenStack Keystone.

- **Severity:** Medium 4.0 (`AV:N/AC:L/Au:S/C:N/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:** 18 Dec 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-w66p-78g4-mr7g, PYSEC-2012-20, RHSA-2012:1557

## What is CVE-2012-5563?

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

### Official description

OpenStack Keystone, as used in OpenStack Folsom 2012.2, does not properly implement token expiration, which allows remote authenticated users to bypass intended authorization restrictions by creating new tokens through token chaining.  NOTE: this issue exists because of a CVE-2012-3426 regression.

Weakness: CWE-255

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

3 open source packages ship an affected version, including keystone. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `keystone` | PyPI | All versions | None |
| `keystone` | PyPI | All versions | 8.0.0 |
| `keystone` | PyPI | All versions | 8.0.0 |
| `openstack-keystone` | Red Hat:openstack:2::el6 | All versions | 0:2012.2.1-1.el6ost |
| `openstack-keystone-doc` | Red Hat:openstack:2::el6 | All versions | 0:2012.2.1-1.el6ost |
| `python-keystone` | Red Hat:openstack:2::el6 | All versions | 0:2012.2.1-1.el6ost |

Products: Openstack Folsom.

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

Upgrade keystone to 8.0.0 or later.

## Is CVE-2012-5563 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-2161](https://insights.sbomify.com/CVE-2013-2161/): OpenStack Swift Unchecked user input in XML responses (high 7.5)
- [CVE-2013-4497](https://insights.sbomify.com/CVE-2013-4497/): OpenStack Compute Nova Improper Access Control (medium 6.4)
- [CVE-2013-1665](https://insights.sbomify.com/CVE-2013-1665/): XML External Entity (XXE) in Django (medium 5.0)
- [CVE-2012-3447](https://insights.sbomify.com/CVE-2012-3447/): Arbitrary file overwrite in OpenStack Nova (medium 4.9)
- [CVE-2012-5625](https://insights.sbomify.com/CVE-2012-5625/): OpenStack Nova Information leak in libvirt LVM-backed instances (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2012-5563 is a medium-severity authentication bypass vulnerability in n/a, published on 18 Dec 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-5563 in the wild and no public exploit code.

Affected packages and fixed versions:
- keystone (PyPI): affected all versions; no fix listed
- keystone (PyPI): affected all versions; fixed in 8.0.0
- keystone (PyPI): affected all versions; fixed in 8.0.0

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

## Sources

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

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