PYSEC-2026-650
Vulnerability from pysec - Published: 2026-07-02 14:13 - Updated: 2026-07-02 14:13OpenStack Keystone Grizzly before 2013.1, Folsom, and possibly earlier allows remote attackers to cause a denial of service (CPU and memory consumption) via a large HTTP request, as demonstrated by a long tenant_name when requesting a token.
| Name | purl | keystone | pkg:pypi/keystone |
|---|
{
"affected": [
{
"package": {
"ecosystem": "PyPI",
"name": "keystone",
"purl": "pkg:pypi/keystone"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "8.0.0a0"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2013-0270",
"GHSA-4ppj-4p4v-jf4p"
],
"details": "OpenStack Keystone Grizzly before 2013.1, Folsom, and possibly earlier allows remote attackers to cause a denial of service (CPU and memory consumption) via a large HTTP request, as demonstrated by a long tenant_name when requesting a token.",
"id": "PYSEC-2026-650",
"modified": "2026-07-02T14:13:22.017502Z",
"published": "2026-07-02T14:13:22.017502Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2013-0270"
},
{
"type": "WEB",
"url": "https://github.com/openstack/keystone/commit/7691276b869a86c2b75631d5bede9f61e030d9d8"
},
{
"type": "WEB",
"url": "https://github.com/openstack/keystone/commit/82c87e5638ebaf9f166a9b07a0155291276d6fdc"
},
{
"type": "WEB",
"url": "https://access.redhat.com/security/cve/CVE-2013-0270"
},
{
"type": "WEB",
"url": "https://bugs.launchpad.net/keystone/+bug/1099025"
},
{
"type": "WEB",
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=909012"
},
{
"type": "WEB",
"url": "https://launchpad.net/keystone/grizzly/2013.1"
},
{
"type": "WEB",
"url": "http://rhn.redhat.com/errata/RHSA-2013-0708.html"
},
{
"type": "PACKAGE",
"url": "https://pypi.org/project/keystone"
},
{
"type": "ADVISORY",
"url": "https://github.com/advisories/GHSA-4ppj-4p4v-jf4p"
}
],
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
],
"summary": "OpenStack Keystone Denial of Service vulnerability via a large HTTP request"
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.