CVE-2018-20345
First published: Fri Dec 21 2018(Updated: )
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. Enterprise editions with RBAC enabled are not affected.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Stackstorm Stackstorm | <2.9.2 | |
| Stackstorm Stackstorm | >=2.10.0<2.10.1 |
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.
Frequently Asked Questions
What is the vulnerability ID for this issue?
The vulnerability ID for this issue is CVE-2018-20345.
What is the severity of CVE-2018-20345?
The severity of CVE-2018-20345 is medium with a severity value of 5.3.
What is affected by CVE-2018-20345?
StackStorm versions before 2.9.2 and 2.10.x before 2.10.1 are affected by CVE-2018-20345.
How can an attacker exploit CVE-2018-20345?
An attacker with a StackStorm account and authenticated against the StackStorm API can exploit CVE-2018-20345 to retrieve datastore items for other users by utilizing specific parameters in the API request.
Is there a fix for CVE-2018-20345?
Yes, the fix for CVE-2018-20345 is available in StackStorm versions 2.9.2 and 2.10.1.
- collector/nvd-index
- agent/severity
- agent/author
- agent/references
- agent/tags
- agent/type
- agent/event
- agent/description
- agent/last-modified-date
- agent/softwarecombine
- agent/first-publish-date
- collector/mitre-cve
- source/MITRE
- vendor/stackstorm
- canonical/stackstorm stackstorm
- version/stackstorm stackstorm/2.10.0