Path Traversal in rasa (CVE-2021-41127)
Summary
Path traversal in rasa (CVE-2021-41127). Data can be tampered with by attackers. Mitigation: upgrade to 2.8.10 or later.
Original description
The description as published by the source.
Impact
An Archive Extraction (Zip Slip) vulnerability in the functionality that allows a user to load a trained model archive in Rasa 2.8.9 and older allows an attacker arbitrary write capability within specific directories using a malicious crafted archive file.
Patches
The vulnerability is fixed in Rasa 2.8.10
Workarounds
Mitigating steps for vulnerable end users are to ensure that they do not upload untrusted model files, and restrict CLI or API endpoint access where a malicious actor could target a deployed Rasa instance.
For more information
If you have any questions or comments about this advisory:
- Email the Rasa Security Team
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-41127 has been found in rasa.
Data can be tampered with by attackers.
What to do: upgrade rasa to 2.8.10 or later.
If unsure, ask your IT team or search "rasa CVE-2021-41127" on the vendor's site.
CVE-2021-41127 (rasa) — CWE-22
Attack vector: remote (network-reachable)
Patched: 2.8.10 — apply immediately
Workaround: Mitigating steps for vulnerable end users are to ensure that they do not upload untrusted model files, and restrict CLI or API endpoint access where a malicious actor could target a deployed Rasa instance.
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 rasa.
Check the vendor advisory for the affected versions of rasa.
Severity: ?. Data can be tampered with by attackers.
Update to 2.8.10.
Workaround: Mitigating steps for vulnerable end users are to ensure that they do not upload untrusted model files, and restrict CLI or API endpoint access where a malicious actor could target a deployed Rasa instance.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'rasa' . 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 'rasa' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
rasaを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
Mitigating steps for vulnerable end users are to ensure that they do not upload untrusted model files, and restrict CLI or API endpoint access where a malicious actor could target a deployed Rasa instance.パッチが適用されるまでの応急処置として、Mitigating steps for vulnerable end users are to ensure that they do not upload untrusted model files, and restrict CLI or API endpoint access where a malicious actor could target a deployed Rasa instance. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade rasa to 2.8.10ステージング環境で 2.8.10 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- package github.com
- web github.com
- web github.com
- web github.com