CVE-2018-20345
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIncorrect 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceStackStorm's st2api incorrectly enforces access control on the /v1/keys datastore endpoint. Authenticated users can retrieve datastore items for other users by including '?scope=all' and '?user=<username>' query parameters, allowing unauthorized cross-user data access.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2.9.2>= 2.10.0, < 2.10.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed StackStorm versionRun 'st2 --version' or check the st2 package version via 'pip show st2' or your package managerAffected if Version is less than 2.9.2, or between 2.10.0 and 2.10.1 (inclusive of 2.10.0, exclusive of 2.10.1)
-
Confirm st2api component is runningCheck if the st2api service is active via 'systemctl status st2api' or equivalent process listingAffected if st2api is running and accessible on the API endpoint
-
Verify RBAC is not enabled in Enterprise editionCheck StackStorm configuration files (typically in /etc/st2) for RBAC settings, or run 'st2rbac' commands if availableAffected if RBAC is disabled or not configured, and the version is in the affected range
-
Test cross-user datastore access vulnerabilityAuthenticate as a regular user, then send a GET request to /v1/keys?scope=all&user=<another_username> using curl or similar toolAffected if The API returns datastore items belonging to the specified other user without authorization errors
If StackStorm version is in the affected range (< 2.9.2 or >= 2.10.0 to < 2.10.1) AND the /v1/keys endpoint responds with data from other users when using ?scope=all&user=<username> parameters, the environment is vulnerable to CVE-2018-20345.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data2.9.22.10.1
Upgrade to StackStorm version 2.9.2 or 2.10.1 or later which contains proper authorization checks. Alternatively, enable RBAC in Enterprise edition.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-20345 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-20345 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data