CVE-2017-16613 OpenStack Swauth object/proxy server writing Auth Token to log file

Critical 9.8 Published Updated

Attackers can steal unhashed authentication tokens from log files to bypass authentication in OpenStack Swift deployments using Swauth.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2017-16613?

CVE-2017-16613 is a critical vulnerability in Debian Debian Linux, published on 21 Nov 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

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.

Weakness: CWE-287

Which versions are affected by CVE-2017-16613?

3 open source packages ship an affected version, including swauth. It affects 3 products.

PackageAffectedFixed in
swauth PyPIAll versions1.3.0
swauth PyPIAll versions1.3.0
swauth PyPIAll versions1.3.0

Products include Debian Debian Linux, Openstack Swauth, Openstack Swift.

How do I fix CVE-2017-16613?

Upgrade swauth to 1.3.0 or later.

Is CVE-2017-16613 being exploited?

There is no known exploitation of CVE-2017-16613 in the wild and no public exploit code.

All Debian Debian Linux vulnerabilities

Sources

Also known as DSA-4044-1, GHSA-qhq8-xwqv-pvv9, PYSEC-2017-84, UBUNTU-CVE-2017-16613.

Is CVE-2017-16613 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free