RASA-PRO · CVE-2024-49375 · Package
FIX → 3.10.12 · 3.6.21 +2
Rasa Pro and Rasa Open Source let a model be loaded remotely through the HTTP API, and a maliciously crafted model can execute code on the instance. An attacker who can load a model gets remote code execution, and with the API open and no authentication this needs no login.
first public Jan 14, 2025 · 2 sources
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Exposure requires the HTTP API to be enabled, which is not the default, so teams running Rasa without --enable-api are not exposed. Unauthenticated exploitation also requires that no authentication or recommended security controls are configured; authenticated exploitation requires a valid token or JWT. Teams that load models from outside their own CI pipeline are most at risk.
Not affected if api-disabled, auth-configured, default-config
Who cares ml-chatbots, python, rasa
pip show rasa-pro or pip show rasa.A vulnerability has been identified in Rasa Pro and Rasa Open Source that enables an attacker who has the ability to load a maliciously crafted model remotely into a Rasa instance to achieve Remote Code Execution.
The prerequisites for this are:
--enable-api. This is not the default configuration.We encourage you to upgrade to a version of Rasa that includes a fix. These are:
Once you have upgraded your Rasa Pro or Open Source installation, you will need to retrain your model using the fixed version of Rasa Pro or Open Source. If you have a custom component that inherits from one of the components listed below and modified the persist or load method, make sure to update your code. Please contact us in case you encounter any problems.
Affected components:
CountVectorFeaturizerLexicalSyntacticFeaturizerLogisticRegressionClassifierAre you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.
--enable-apiUpgrade to 3.10.12 · 3.6.21 +2
3.8.18, 3.9.16 or 3.10.12 depending on the branch in use.3.6.21.SklearnIntentClassifierDIETClassifierCRFEntityExtractorTrackerFeaturizerTEDPolicyUnexpectedIntentTEDPolicyIf you are unable to upgrade immediately, please follow our mitigation advice below.
The unauthenticated RCE can be mitigated by ensuring that you enable authentication for the Rasa HTTP API if this is enabled. This means that in addition to passing --enable-api to Rasa, you should also pass an authentication configuration as described in our documentation here.
The authenticated RCE can be mitigated by:
As an additional security step, a future release of Rasa Pro will remove the ability to enable the API without any authentication method enabled.
Rasa would like to thank Julian Scheid from Deutsche Telekom Security GmbH for responsible disclosure of this vulnerability.
This page as .md · .json · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
GitHub Advisory Database, CC-BY 4.0 · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.