PYSEC-2020-56
Vulnerability from pysec - Published: 2020-05-07 00:15 - Updated: 2020-09-02 16:15An issue was discovered in OpenStack Keystone before 15.0.1, and 16.0.0. The EC2 API doesn't have a signature TTL check for AWS Signature V4. An attacker can sniff the Authorization header, and then use it to reissue an OpenStack token an unlimited number of times.
| Name | purl | keystone | pkg:pypi/keystone |
|---|
{
"affected": [
{
"package": {
"ecosystem": "PyPI",
"name": "keystone",
"purl": "pkg:pypi/keystone"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "15.0.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"12.0.2",
"12.0.3",
"13.0.2",
"13.0.3",
"13.0.4",
"14.0.0",
"14.0.1",
"14.1.0",
"14.2.0",
"15.0.0.0rc1",
"15.0.0.0rc2",
"15.0.0"
]
}
],
"aliases": [
"CVE-2020-12692",
"GHSA-rqw2-hhrf-7936"
],
"details": "An issue was discovered in OpenStack Keystone before 15.0.1, and 16.0.0. The EC2 API doesn\u0027t have a signature TTL check for AWS Signature V4. An attacker can sniff the Authorization header, and then use it to reissue an OpenStack token an unlimited number of times.",
"id": "PYSEC-2020-56",
"modified": "2020-09-02T16:15:00Z",
"published": "2020-05-07T00:15:00Z",
"references": [
{
"type": "WEB",
"url": "https://www.openwall.com/lists/oss-security/2020/05/06/4"
},
{
"type": "WEB",
"url": "https://bugs.launchpad.net/keystone/+bug/1872737"
},
{
"type": "WEB",
"url": "http://www.openwall.com/lists/oss-security/2020/05/07/1"
},
{
"type": "WEB",
"url": "https://security.openstack.org/ossa/OSSA-2020-003.html"
},
{
"type": "WEB",
"url": "https://usn.ubuntu.com/4480-1/"
},
{
"type": "ADVISORY",
"url": "https://github.com/advisories/GHSA-rqw2-hhrf-7936"
}
]
}
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.