CVE-2017-16613

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 2.3%, top 15% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 8%CVSS: 9.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
9.8
EG Score
9.8(medium)
EPSS
94.3%
KEV
Not listed

Published

November 21, 2017

Last Modified

May 13, 2026

Advisory Details (5)

Auto-updated Jun 22, 2026
Patch available. Sources: github_commit.
generic

[SECURITY] [DSA 4044-1] swauth security update

https://www.debian.org/security/2017/dsa-4044
github_commit

commit 70af7986265a (openstack/swauth)

Fix landed in openstack/swauth commit 70af7986265a — awaiting tagged release

https://github.com/openstack/swauth/commit/70af7986265a3defea054c46efc82d0698917298
generic

Bug #1655781 “Swift object/proxy server writing Auth Token to lo...” : Bugs : OpenStack Object Storage (swift)

https://bugs.launchpad.net/swift/+bug/1655781
generic Patch Available

#882314 - swauth: Swift object/proxy server writing swauth Auth Token to log file (CVE-2017-16613) - Debian Bug report logs

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882314
generic
http://www.securityfocus.com/bid/101926

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
swauth1.0.8 ... 1.0.1 (9 versions)1.3.0—

Data Freshness Timeline

(refreshed 8× in last 7d / 36× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-16 16:59 UTCEPSS rescore
  2. 2026-07-16 16:59 UTCEPSS rescore
  3. 2026-07-15 16:54 UTCEPSS rescore
  4. 2026-07-15 16:54 UTCEPSS rescore
  5. 2026-07-15 01:56 UTCEPSS rescore
  6. 2026-07-13 22:26 UTCEPSS rescore
  7. 2026-07-12 05:43 UTCEPSS rescore
  8. 2026-07-11 08:24 UTCEPSS rescore
  9. 2026-07-09 19:06 UTCEPSS rescore
  10. 2026-07-08 15:10 UTCEPSS rescore
  11. 2026-07-07 23:27 UTCOSV refresh
  12. 2026-07-07 13:42 UTCEPSS rescore
  13. 2026-07-06 16:24 UTCEPSS rescore
  14. 2026-07-06 02:20 UTCEPSS rescore
  15. 2026-07-05 02:27 UTCEPSS rescore
  16. 2026-07-04 06:28 UTCEPSS rescore
  17. 2026-07-01 15:02 UTCEPSS rescore
  18. 2026-07-01 15:02 UTCEPSS rescore
  19. 2026-06-30 23:19 UTCEPSS rescore
  20. 2026-06-30 23:19 UTCEPSS rescore
  21. 2026-06-28 14:04 UTCEPSS rescore
  22. 2026-06-28 04:53 UTCEPSS rescore
  23. 2026-06-27 03:05 UTCEPSS rescore
  24. 2026-06-25 13:47 UTCEPSS rescore
  25. 2026-06-25 13:47 UTCEPSS rescore
Show 55 more
  1. 2026-06-24 14:02 UTCEPSS rescore
  2. 2026-06-23 21:30 UTCEPSS rescore
  3. 2026-06-22 14:23 UTCEPSS rescore
  4. 2026-06-22 14:23 UTCEPSS rescore
  5. 2026-06-21 14:54 UTCEPSS rescore
  6. 2026-06-21 14:54 UTCEPSS rescore
  7. 2026-06-21 01:57 UTCEPSS rescore
  8. 2026-06-21 01:57 UTCEPSS rescore
  9. 2026-06-19 11:25 UTCOSV refresh
  10. 2026-06-18 17:50 UTCEPSS rescore
  11. 2026-06-17 17:50 UTCEPSS rescore
  12. 2026-06-16 17:50 UTCEPSS rescore
  13. 2026-06-15 17:45 UTCEPSS rescore
  14. 2026-06-14 23:14 UTCEPSS rescore
  15. 2026-06-14 23:14 UTCEPSS rescore
  16. 2026-06-13 22:57 UTCEPSS rescore
  17. 2026-06-12 23:09 UTCEPSS rescore
  18. 2026-06-11 13:57 UTCEPSS rescore
  19. 2026-06-10 22:15 UTCEPSS rescore
  20. 2026-06-08 14:14 UTCEPSS rescore
  21. 2026-06-07 15:22 UTCEPSS rescore
  22. 2026-06-07 15:22 UTCEPSS rescore
  23. 2026-06-06 13:45 UTCEPSS rescore
  24. 2026-06-06 13:45 UTCEPSS rescore
  25. 2026-06-05 22:44 UTCEPSS rescore
  26. 2026-06-05 06:08 UTCEPSS rescore
  27. 2026-06-05 06:08 UTCEPSS rescore
  28. 2026-06-04 13:10 UTCEPSS rescore
  29. 2026-06-04 13:10 UTCEPSS rescore
  30. 2026-06-02 20:11 UTCEPSS rescore
  31. 2026-06-02 20:11 UTCEPSS rescore
  32. 2026-06-01 13:49 UTCEPSS rescore
  33. 2026-06-01 13:49 UTCEPSS rescore
  34. 2026-05-31 22:28 UTCEPSS rescore
  35. 2026-05-31 00:14 UTCEPSS rescore
  36. 2026-05-30 19:53 UTCOSV refresh
  37. 2026-05-29 13:41 UTCEPSS rescore
  38. 2026-05-28 13:42 UTCEPSS rescore
  39. 2026-05-28 13:42 UTCEPSS rescore
  40. 2026-05-27 13:38 UTCEPSS rescore
  41. 2026-05-27 13:38 UTCEPSS rescore
  42. 2026-05-26 13:42 UTCEPSS rescore
  43. 2026-05-26 13:42 UTCEPSS rescore
  44. 2026-05-26 07:17 UTCEPSS rescore
  45. 2026-05-26 07:17 UTCEPSS rescore
  46. 2026-05-22 21:15 UTCEPSS rescore
  47. 2026-05-22 21:15 UTCEPSS rescore
  48. 2026-05-22 21:15 UTCEPSS rescore
  49. 2026-05-20 22:37 UTCEPSS rescore
  50. 2026-05-20 22:37 UTCEPSS rescore
  51. 2026-05-20 11:21 UTCEPSS rescore
  52. 2026-05-20 11:21 UTCEPSS rescore
  53. 2026-05-18 23:25 UTCEG score recompute
  54. 2026-05-18 21:30 UTCEPSS rescore
  55. 2026-05-18 21:30 UTCEPSS rescore

Frequently asked(5)

What is CVE-2017-16613?
CVE-2017-16613 is a critical vulnerability published on November 21, 2017. 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…
When was CVE-2017-16613 disclosed?
CVE-2017-16613 was first published in the National Vulnerability Database on November 21, 2017, with the most recent update on May 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-16613 actively exploited?
CVE-2017-16613 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 94.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2017-16613?
CVE-2017-16613 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2017-16613?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-16613, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2017-16613

Explore →

Is Your Infrastructure Affected by CVE-2017-16613?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs