First published: Tue Nov 21 2017(Updated: )
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.
Credit: cve@mitre.org cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
OpenStack Swauth | <=1.2.0 | |
OpenStack Swift | <=2.15.1 | |
Debian Debian Linux | =9.0 | |
pip/swauth | <1.3.0 | 1.3.0 |
debian/swauth | <=1.2.0-1<=1.2.0-3 | 1.2.0-4 1.2.0-2+deb9u1 |
debian/swauth |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of CVE-2017-16613 is 9.8 (Critical).
The affected software includes OpenStack Swauth versions up to 1.3.0-2 and OpenStack Swift versions up to 2.15.1.
CVE-2017-16613 allows unhashed tokens retrieved from the Swauth middleware authentication mechanism to be saved to a log file as part of a GET URI.
To fix CVE-2017-16613, update OpenStack Swauth to version 1.3.0-2 or later.
Additional information about CVE-2017-16613 can be found at the following references: [1](https://bugs.launchpad.net/swift/+bug/1655781), [2](https://security-tracker.debian.org/tracker/CVE-2017-16613), [3](http://127.0.0.1:8080/auth/v1.0)