PYSEC-2017-84
Vulnerability from pysec - Published: 2017-11-21 13:29 - Updated: 2021-08-25 04:30An issue was discovered in middleware.py in OpenStack Swauth through 1.2.0 when used with OpenStack Swift through 2.15.1. The Swift object store and proxy server are saving (unhashed) tokens retrieved from the Swauth middleware authentication mechanism to a log file as part of a GET URI. This allows attackers to bypass authentication by inserting a token into an X-Auth-Token header of a new request. NOTE: github.com/openstack/swauth URLs do not mean that Swauth is maintained by an official OpenStack project team.
| Name | purl | swauth | pkg:pypi/swauth |
|---|
{
"affected": [
{
"package": {
"ecosystem": "PyPI",
"name": "swauth",
"purl": "pkg:pypi/swauth"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "70af7986265a3defea054c46efc82d0698917298"
}
],
"repo": "https://github.com/openstack/swauth",
"type": "GIT"
},
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.3.0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.0.8",
"1.1.0",
"1.2.0"
]
}
],
"aliases": [
"CVE-2017-16613",
"GHSA-qhq8-xwqv-pvv9"
],
"details": "An issue was discovered in middleware.py in OpenStack Swauth through 1.2.0 when used with OpenStack Swift through 2.15.1. The Swift object store and proxy server are saving (unhashed) tokens retrieved from the Swauth middleware authentication mechanism to a log file as part of a GET URI. This allows attackers to bypass authentication by inserting a token into an X-Auth-Token header of a new request. NOTE: github.com/openstack/swauth URLs do not mean that Swauth is maintained by an official OpenStack project team.",
"id": "PYSEC-2017-84",
"modified": "2021-08-25T04:30:33.081491Z",
"published": "2017-11-21T13:29:00Z",
"references": [
{
"type": "FIX",
"url": "https://github.com/openstack/swauth/commit/70af7986265a3defea054c46efc82d0698917298"
},
{
"type": "WEB",
"url": "https://bugs.launchpad.net/swift/+bug/1655781"
},
{
"type": "WEB",
"url": "https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882314"
},
{
"type": "ADVISORY",
"url": "https://www.debian.org/security/2017/dsa-4044"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/bid/101926"
},
{
"type": "ADVISORY",
"url": "https://github.com/advisories/GHSA-qhq8-xwqv-pvv9"
}
]
}
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.
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.