CVE-2017-16613Not scoredCWE-287

CVE-2017-16613: Openstack Swauth vulnerability

Openstack · Swauth

Vendor fix available · Affected: Openstack Swauth · Exploitation: possible (1 to 10%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

8.6%probability of exploitation in the next 30 days

95th percentile

050100

Higher than 95% of scored CVEs

Not scored yet. The CVE record carries no CVSS score.

DescriptionCVE.org

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.

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas

Exploitation: Possible (1 to 10%). EPSS between 1% and 10%.
CISA KEV: Not listed
Public check: No public nuclei template
Weakness: Improper Authentication · Authentication
Vendor: Openstack
Published: November 2017
Band: Possible (1 to 10%), November 2017

CoverageNo articles yet

No CyberSIXT article names CVE-2017-16613 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.