Skip to main content

Over 150 LLM Providers · Over 5,300 Models The most extensible AI-powered pentesting platform. Open source. Star on GitHub

CVE-2017-16613

9.8 · CRITICAL
Published Nov 21, 2017 openstack CWE-287 EPSS 8.42% (95th pctl)

Overview

CVE-2017-16613 is a critical-severity vulnerability affecting openstack swauth. It was published on November 21, 2017 and has a CVSS 3.0 base score of 9.8 (CRITICAL).

This vulnerability has a CVSS 3.0 base score of 9.8, rated CRITICAL. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

Technical 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.

Remediation

Check the references section for vendor advisories and patches from openstack. Update swauth to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Affected Products

Vendor Product Versions Status
openstack swauth 0 Affected
openstack swift 0 Affected

Frequently Asked Questions

What is CVE-2017-16613?

CVE-2017-16613 is a critical-severity vulnerability affecting openstack swauth. It was published on November 21, 2017 and has a CVSS 3.0 base score of 9.8 (CRITICAL).

How severe is CVE-2017-16613?

This vulnerability has a CVSS 3.0 base score of 9.8, rated CRITICAL. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2017-16613?

Check the references section for vendor advisories and patches from openstack. Update swauth to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2017-16613?

CyberStrike's AI-powered security agents can automatically detect CVE-2017-16613 across your infrastructure using autonomous pentesting, DAST scanning, and HackBrowser. The platform continuously monitors for known vulnerabilities and provides actionable remediation guidance prioritized by real-world exploitability.