OpenStack Swauth object/proxy server writing Auth Token to log file
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.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2017-16613US | critical9.8 | — | ||
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 (unhash… | ||||
references
External citations — patches, advisories, analysis.
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882314WEB
- https://bugs.launchpad.net/swift/+bug/1655781WEB
- https://github.com/openstack/swauthPACKAGE
- https://github.com/openstack/swauth/commit/70af7986265a3defea054c46efc82d0698917298WEB
- https://github.com/pypa/advisory-database/tree/main/vulns/swauth/PYSEC-2017-84.yamlWEB
- https://nvd.nist.gov/vuln/detail/CVE-2017-16613ADVISORY
- https://web.archive.org/web/20200227140059/http://www.securityfocus.com/bid/101926WEB
- https://www.debian.org/security/2017/dsa-4044WEB
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan