Path Traversal in github.com/sassoftware/go-rpmutils (CVE-2020-7667)
Summary
Path traversal in github.com/sassoftware/go-rpmutils (CVE-2020-7667). Data can be tampered with by attackers. Mitigation: upgrade to 0.1.0 or later.
Original description
The description as published by the source.
In package github.com/sassoftware/go-rpmutils/cpio before version 0.1.0, the CPIO extraction functionality doesn't sanitize the paths of the archived files for leading and non-leading ".." which leads in file extraction outside of the current directory. Note: the fixing commit was applied to all affected versions which were re-released.
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-2020-7667 has been found in github.com/sassoftware/go-rpmutils.
Data can be tampered with by attackers.
What to do: upgrade github.com/sassoftware/go-rpmutils to 0.1.0 or later.
If unsure, ask your IT team or search "github.com/sassoftware/go-rpmutils CVE-2020-7667" on the vendor's site.
CVE-2020-7667 (github.com/sassoftware/go-rpmutils) — CWE-22
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 0.1.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.
Path traversal (CWE-22) exists in github.com/sassoftware/go-rpmutils.
Check the vendor advisory for the affected versions of github.com/sassoftware/go-rpmutils.
Severity: ?. Data can be tampered with by attackers.
Update to 0.1.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/sassoftware/go-rpmutils' . 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 'github.com/sassoftware/go-rpmutils' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/sassoftware/go-rpmutilsを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/sassoftware/go-rpmutils to 0.1.0ステージング環境で 0.1.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- patch github.com
- report snyk.io
- web pkg.go.dev
- web snyk.io