Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2017-16613 critical CVSS 9.8

Authentication Bypass in swauth (CVE-2017-16613)

Summary

Authentication bypass in swauth (CVE-2017-16613). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 70af7986265a3defea054c46efc82d0698917298, 1.3.0 or later.

Original description

The description as published by the source.

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.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2017-16613 has been found in swauth.
Successful exploitation can lead to full system takeover. CVSS score: 9.8/10.
What to do: upgrade swauth to 70af7986265a3defea054c46efc82d0698917298, 1.3.0 or later.
If unsure, ask your IT team or search "swauth CVE-2017-16613" on the vendor's site.

CVE-2017-16613 (swauth) — CWE-287 / CVSS v3 9.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 70af7986265a3defea054c46efc82d0698917298, 1.3.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Authentication bypass (CWE-287) exists in swauth.

📍 Affected scope

Check the vendor advisory for the affected versions of swauth.

🔥 Severity

Severity: Critical (CVSS 9.8/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 70af7986265a3defea054c46efc82d0698917298, 1.3.0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'swauth' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'swauth' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で swauth を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade swauth to 70af7986265a3defea054c46efc82d0698917298, 1.3.0

    ステージング環境で 70af7986265a3defea054c46efc82d0698917298, 1.3.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

PyPI swauth
[{"repo":"https:\/\/github.com\/openstack\/swauth","type":"GIT","events":[{"introduced":"0"},{"fixed":"70af7986265a3defea054c46efc82d0698917298"}]},{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.3.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details