Skip to content

OpenStack Swauth object/proxy server writing Auth Token to log file

Critical severity GitHub Reviewed Published May 17, 2022 to the GitHub Advisory Database • Updated May 1, 2024

Package

pip swauth (pip)

Affected versions

< 1.3.0

Patched versions

1.3.0

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.

References

Published by the National Vulnerability Database Nov 21, 2017
Published to the GitHub Advisory Database May 17, 2022
Reviewed May 1, 2024
Last updated May 1, 2024

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS score

0.439%
(75th percentile)

Weaknesses

CVE ID

CVE-2017-16613

GHSA ID

GHSA-qhq8-xwqv-pvv9

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.