Path Traversal in nemo-toolkit (CVE-2022-22821)
Summary
Path traversal in nemo-toolkit (CVE-2022-22821). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.6.0 or later.
Original description
The description as published by the source.
NVIDIA NeMo before 1.6.0 contains a vulnerability in ASR WebApp, in which ../ Path Traversal may lead to deletion of any directory when admin privileges are available.
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-2022-22821 has been found in nemo-toolkit.
Risk of unauthorized operations or information disclosure.
What to do: upgrade nemo-toolkit to 1.6.0 or later.
If unsure, ask your IT team or search "nemo-toolkit CVE-2022-22821" on the vendor's site.
CVE-2022-22821 (nemo-toolkit) — CWE-22
Attack vector: local
Patched: 1.6.0 — apply immediately
Workaround: The changes in commit https://github.com/NVIDIA/NeMo/commit/f7e4ed7e4f7f2fa43765a38c2fafa1b6d1ebd7c0 can be applied to any version of the web app without any adverse effect.
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 nemo-toolkit.
Check the vendor advisory for the affected versions of nemo-toolkit.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 1.6.0.
Workaround: The changes in commit https://github.com/NVIDIA/NeMo/commit/f7e4ed7e4f7f2fa43765a38c2fafa1b6d1ebd7c0 can be applied to any version of the web app without any adverse effect.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'nemo-toolkit' . 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 'nemo-toolkit' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
nemo-toolkitを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
The changes in commit https://github.com/NVIDIA/NeMo/commit/f7e4ed7e4f7f2fa43765a38c2fafa1b6d1ebd7c0 can be applied to any version of the web app without any adverse effect.パッチが適用されるまでの応急処置として、The changes in commit https://github.com/NVIDIA/NeMo/commit/f7e4ed7e4f7f2fa43765a38c2fafa1b6d1ebd7c0 can be applied to any version of the web app without any adverse effect. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade nemo-toolkit to 1.6.0ステージング環境で 1.6.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com