Vulnerabilities > Stackstorm
DATE | CVE | VULNERABILITY TITLE | RISK |
---|---|---|---|
2022-12-06 | CVE-2022-44009 | Missing Authorization vulnerability in Stackstorm 3.7.0 Improper access control in Key-Value RBAC in StackStorm version 3.7.0 didn't check the permissions in Jinja filters, allowing attackers to access K/V pairs of other users, potentially leading to the exposure of sensitive Information. | 7.5 |
2022-12-05 | CVE-2022-43706 | Cross-site Scripting vulnerability in Stackstorm Cross-site scripting (XSS) vulnerability in the Web UI of StackStorm versions prior to 3.8.0 allowed logged in users with write access to pack rules to inject arbitrary script or HTML that may be executed in Web UI for other logged in users. | 5.4 |
2021-12-15 | CVE-2021-44657 | Unspecified vulnerability in Stackstorm 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. | 8.8 |
2021-03-18 | CVE-2021-28667 | Infinite Loop vulnerability in Stackstorm StackStorm before 3.4.1, in some situations, has an infinite loop that consumes all available memory and disk space. | 7.5 |
2019-03-09 | CVE-2019-9580 | Cross-site Scripting vulnerability in Stackstorm In st2web in StackStorm Web UI before 2.9.3 and 2.10.x before 2.10.3, it is possible to bypass the CORS protection mechanism via a "null" origin value, potentially leading to XSS. | 6.1 |
2018-12-21 | CVE-2018-20345 | Unspecified vulnerability in Stackstorm Incorrect access control in StackStorm API (st2api) in StackStorm before 2.9.2 and 2.10.x before 2.10.1 allows an attacker (who has a StackStorm account and is authenticated against the StackStorm API) to retrieve datastore items for other users by utilizing the /v1/keys "?scope=all" and "?user=<username>" query filter parameters. | 5.3 |