CVE-2021-44657
First published: Wed Dec 15 2021(Updated: )
In StackStorm versions prior to 3.6.0, the jinja interpreter was not run in sandbox mode and thus allows execution of unsafe system commands. Jinja does not enable sandboxed mode by default due to backwards compatibility. Stackstorm now sets sandboxed mode for jinja by default.
Credit: cve@mitre.org cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Stackstorm Stackstorm | <3.6.0 | |
| <3.6.0 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the vulnerability ID for this issue?
The vulnerability ID for this issue is CVE-2021-44657.
What is the severity of CVE-2021-44657?
The severity of CVE-2021-44657 is critical with a CVSS score of 8.8.
What is the affected software for CVE-2021-44657?
The affected software for CVE-2021-44657 is StackStorm versions prior to 3.6.0.
How does CVE-2021-44657 allow execution of unsafe system commands?
In StackStorm versions prior to 3.6.0, the jinja interpreter was not run in sandbox mode, allowing execution of unsafe system commands.
How do I fix CVE-2021-44657?
To fix CVE-2021-44657, upgrade to StackStorm version 3.6.0 or later.
- collector/nvd-index
- agent/references
- agent/type
- collector/mitre-cve
- source/MITRE
- agent/severity
- agent/remedy
- agent/first-publish-date
- agent/description
- collector/nvd-api
- source/NVD
- agent/software-canonical-lookup
- agent/last-modified-date
- agent/author
- agent/tags
- agent/softwarecombine
- agent/event
- vendor/stackstorm
- canonical/stackstorm stackstorm