# CVE-2013-0270: Keystone: openstack keystone: denial of service via large http request with long tenant name

> Remote attackers can cause denial of service in OpenStack Keystone by sending large HTTP requests with long tenant names, exhausting system resources.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **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:** 12 Apr 2013
- **Updated:** 30 Jul 2026
- **Also known as:** DEBIAN-CVE-2013-0270, GHSA-4ppj-4p4v-jf4p, PYSEC-2026-650

## What is CVE-2013-0270?

CVE-2013-0270 is a medium-severity denial of service vulnerability in Red Hat OpenStack Folsom for RHEL 6, published on 12 Apr 2013. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A flaw was found in OpenStack Keystone. A remote attacker could exploit this vulnerability by sending a large HTTP request, specifically by providing a long tenant name when requesting a token. This could lead to a denial of service, consuming excessive CPU and memory resources on the affected system.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer), CWE-1284 (Improper Validation of Specified Quantity in Input)

## Which versions are affected by CVE-2013-0270?

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


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

Products: Openstack Keystone.

## How do I fix CVE-2013-0270?

Upgrade keystone to 8.0.0a0 or later.

## Is CVE-2013-0270 being exploited?

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

## Other vulnerabilities in Red Hat OpenStack Folsom for RHEL 6

- [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-2013-0270 and fix it if it is affected.

What it is: CVE-2013-0270 is a medium-severity denial of service vulnerability in Red Hat OpenStack Folsom for RHEL 6, published on 12 Apr 2013. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-0270 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
- 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-2013-0270/ (Markdown: https://insights.sbomify.com/CVE-2013-0270/index.md)
```

## Sources

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

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