← Back
GHSA-qp9x-wp8f-qgjj
Vulnerability in tuf (GHSA-qp9x-wp8f-qgjj)
Summary
vulnerability in tuf (GHSA-qp9x-wp8f-qgjj). Risk of unauthorized operations or information disclosure. Exploitable via ``DelegatedRole._is_target_in_pathpattern``. Mitigation: upgrade to `7.0.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **GHSA-qp9x-wp8f-qgjj** has been found in tuf.
Attackers can target a specific entry point like ``DelegatedRole._is_target_in_pathpattern`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade tuf to **7.0.0** or later.
If unsure, ask your IT team or search "tuf GHSA-qp9x-wp8f-qgjj" on the vendor's site.
GHSA-qp9x-wp8f-qgjj (tuf) — CWE-178 /
Attack vector: local / unauthenticated / no user interaction
Attack surface: `DelegatedRole._is_target_in_pathpattern` / `fnmatch.fnmatch` / `normcase` / `os.path`
Patched: `7.0.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
**A vulnerability** (CWE-178) exists in tuf. Attackers reach the vulnerable code path via ``DelegatedRole._is_target_in_pathpattern`` without authentication.
📍 Affected scope
tuf — . Attack surface: `DelegatedRole._is_target_in_pathpattern` / `fnmatch.fnmatch` / `normcase` / `os.path`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **7.0.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 'tuf' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'tuf' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `tuf` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade tuf to 7.0.0ステージング環境で 7.0.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
pip
tuf
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.0.0"}]}]
PyPI
tuf
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.0.0"}]}]