CVE-2024-36987
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 · uneditedIn Splunk Enterprise versions below 9.2.2, 9.1.5, and 9.0.10 and Splunk Cloud Platform versions below 9.1.2312.200, an authenticated, low-privileged user who does not hold the admin or power Splunk roles could upload a file with an arbitrary extension using the indexing/preview REST endpoint.
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 confidenceA file upload vulnerability in Splunk Enterprise and Cloud Platform allows authenticated low-privileged users (non-admin/non-power roles) to upload files with arbitrary extensions via the indexing/preview REST endpoint. This bypasses intended file type restrictions and could enable malicious file placement or execution.
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>= 9.1.2312, < 9.1.2312.200>= 9.0.0, < 9.0.10>= 9.1.0, < 9.1.5>= 9.2.0, < 9.2.2CVSS 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
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 Splunk versionLog into Splunk Web as admin, go to Settings > About > About Splunk, or run: splunk version via CLIAffected if Version is 9.0.0 through 9.0.9, 9.1.0 through 9.1.4, 9.2.0 through 9.2.1, or 9.1.2312 through 9.1.2312.199 (Cloud)
-
Confirm user role assignments for the indexing/preview endpointNavigate to Settings > Roles or query the auth/roles endpoint via: splunk show user-roles -app searchAffected if Low-privileged users (not admin or power) have access to roles that can reach /services/indexing/preview or /services/search/jobs export
-
Verify if file upload with arbitrary extensions is possibleTest uploading a file with a non-standard extension (e.g., .exe, .php) via REST endpoint: POST to /services/indexing/preview with the file in the 'file' parameterAffected if Low-privileged users can successfully upload files with dangerous extensions that should be blocked by policy
-
Audit recent file uploads to the indexing endpointSearch Splunk internal logs: index=_internal sourcetype=splunkd_ui_access /services/indexing/preview | stats count by user, fileAffected if Low-privileged users have uploaded files with extensions outside the expected set (e.g., scripts, executables)
A user is affected if their Splunk version falls within the affected ranges AND low-privileged (non-admin/non-power) users have access to the indexing/preview REST endpoint.
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.
dbcve · scoped9.0.109.1.59.1.2312.200
Upgrade Splunk Enterprise to versions 9.2.2, 9.1.5, or 9.0.10 (or higher), and Splunk Cloud Platform to version 9.1.2312.200 or higher. Additionally, review and restrict role-based access controls for the indexing/preview endpoint until patches are applied.
Splunk Enterprise 9.2.2, 9.1.5, or 9.0.10; Splunk Cloud Platform 9.1.2312.200
- Identify current Splunk Enterprise version by navigating to Settings > About > About Splunk or running 'splunk --version'
- Determine current version line (9.0.x, 9.1.x, or 9.2.x) to select appropriate upgrade target
- For Splunk Enterprise 9.0.x: Upgrade to version 9.0.10 or later
- For Splunk Enterprise 9.1.x: Upgrade to version 9.1.5 or later
- For Splunk Enterprise 9.2.x: Upgrade to version 9.2.2 or later
- For Splunk Cloud Platform: Upgrade to version 9.1.2312.200 or later
- Review Splunk Upgrade Planning documentation before initiating upgrade
- Test upgrade in non-production environment before applying to production
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.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 $6,080.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-36987 — 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-2024-36987 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