Path Traversal in tough (CVE-2021-41149)
Summary
Path traversal in tough (CVE-2021-41149). Confidential information can be exposed externally. Mitigation: upgrade to 0.12.0 or later.
Original description
The description as published by the source.
Impact
The tough library, prior to 0.12.0, does not properly sanitize target names when caching a repository, or when saving specific targets to an output directory. When targets are cached or saved, files could be overwritten with arbitrary content anywhere on the system.
AWS would like to thank https://github.com/jku for reporting this issue.
Patches
A fix is available in version 0.12.0.
Workarounds
No workarounds to this issue are known.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
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-2021-41149 has been found in tough.
Confidential information can be exposed externally.
What to do: upgrade tough to 0.12.0 or later.
If unsure, ask your IT team or search "tough CVE-2021-41149" on the vendor's site.
CVE-2021-41149 (tough) — CWE-22
Attack vector: remote (network-reachable) / no user interaction
Patched: 0.12.0 — apply immediately
Workaround: No workarounds to this issue are known.
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.
Path traversal (CWE-22) exists in tough.
Check the vendor advisory for the affected versions of tough.
Severity: ?. Confidential information can be exposed externally.
Update to 0.12.0.
Workaround: No workarounds to this issue are known.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'tough' . 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
-
1Identify exposure identify
grep -r 'tough' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
toughを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
No workarounds to this issue are known.パッチが適用されるまでの応急処置として、No workarounds to this issue are known. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade tough to 0.12.0ステージング環境で 0.12.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com