Path Traversal in github.com/in-toto/in-toto-golang (CVE-2021-41087)
Summary
Path traversal in github.com/in-toto/in-toto-golang (CVE-2021-41087). Data can be tampered with by attackers. Mitigation: upgrade to 0.3.0 or later.
Original description
The description as published by the source.
Impact
Authenticated attackers posing as functionaries (i.e., within a trusted set of users for a layout) are able to create attestations that may bypass DISALLOW rules in the same layout. An attacker with access to trusted private keys, may issue an attestation that contains a disallowed artifact by including path traversal semantics (e.g., foo vs dir/../foo).
Patches
The problem has been fixed in version 0.3.0.
Workarounds
Exploiting this vulnerability is dependent on the specific policy applied.
For more information
If you have any questions or comments about this advisory:
- Open an issue in in-toto-golang
- Email us at in-toto-public
- If this is a sensitive security-relevant disclosure, please send a PGP encrypted email to santiagotorres@purdue.edu or jcappos@nyu.edu
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-41087 has been found in github.com/in-toto/in-toto-golang.
Data can be tampered with by attackers.
What to do: upgrade github.com/in-toto/in-toto-golang to 0.3.0 or later.
If unsure, ask your IT team or search "github.com/in-toto/in-toto-golang CVE-2021-41087" on the vendor's site.
CVE-2021-41087 (github.com/in-toto/in-toto-golang) — CWE-22
Attack vector: local / no user interaction
Patched: 0.3.0 — apply immediately
Workaround: Exploiting this vulnerability is dependent on the specific policy applied.
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/in-toto/in-toto-golang.
Check the vendor advisory for the affected versions of github.com/in-toto/in-toto-golang.
Severity: ?. Data can be tampered with by attackers.
Update to 0.3.0.
Workaround: Exploiting this vulnerability is dependent on the specific policy applied.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/in-toto/in-toto-golang' . 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/in-toto/in-toto-golang' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/in-toto/in-toto-golangを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
Exploiting this vulnerability is dependent on the specific policy applied.パッチが適用されるまでの応急処置として、Exploiting this vulnerability is dependent on the specific policy applied. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade github.com/in-toto/in-toto-golang to 0.3.0ステージング環境で 0.3.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