Path Traversal in github.com/deislabs/oras (CVE-2021-21272)
Summary
Path traversal in github.com/deislabs/oras (CVE-2021-21272). Data can be tampered with by attackers. Exploitable via oras. Mitigation: upgrade to 0.9.0 or later.
Original description
The description as published by the source.
Impact
The directory support (#55) allows the downloaded gzipped tarballs to be automatically extracted to the user-specified directory where the tarball can have symbolic links and hard links.
A well-crafted tarball or tarballs allow malicious artifact providers linking, writing, or overwriting specific files on the host filesystem outside of the user-specified directory unexpectedly with the same permissions as the user who runs oras pull.
Precisely, the following users of the affected versions are impacted
orasCLI users who runsoras pull.- Go programs, which invokes
github.com/deislabs/oras/pkg/content.FileStore.
Patches
The problem has been patched by the PR linked with this advisory. Users should upgrade their oras CLI and packages to 0.9.0.
Workarounds
For oras CLI users, there is no workarounds other than pulling from a trusted artifact provider.
For oras package users, the workaround is to not use github.com/deislabs/oras/pkg/content.FileStore, and use other content stores instead, or pull from a trusted artifact provider.
References
For more information
If you have any questions or comments about this advisory:
- Open an issue on the GitHub repo
- Email the list of maintainers
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-21272 has been found in github.com/deislabs/oras.
Attackers can target a specific entry point like oras over the network to misuse the product.
Data can be tampered with by attackers.
What to do: upgrade github.com/deislabs/oras to 0.9.0 or later.
If unsure, ask your IT team or search "github.com/deislabs/oras CVE-2021-21272" on the vendor's site.
CVE-2021-21272 (github.com/deislabs/oras) — CWE-22
Attack vector: remote (network-reachable) / no user interaction
Attack surface: oras
Patched: 0.9.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/deislabs/oras. Attackers reach the vulnerable code path via oras.
Check the vendor advisory for the affected versions of github.com/deislabs/oras. Attack surface: oras.
Severity: ?. Data can be tampered with by attackers.
Update to 0.9.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/deislabs/oras' . 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/deislabs/oras' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/deislabs/orasを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/deislabs/oras to 0.9.0ステージング環境で 0.9.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-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
- web github.com
- web pkg.go.dev
- web pkg.go.dev