CVE-2024-36994
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 and 9.1.2308.207, a low-privileged user that does not hold the admin or power Splunk roles could craft a malicious payload through a View and Splunk Web Bulletin Messages that could result in execution of unauthorized JavaScript code in the browser of a user.
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 stored cross-site scripting (XSS) vulnerability in Splunk Enterprise and Cloud Platform allows low-privileged users (non-admin/non-power roles) to inject malicious JavaScript payloads through View and Splunk Web Bulletin Messages. When other users view these messages, the embedded JavaScript executes in their browsers, potentially enabling session hijacking, credential theft, or actions on behalf of authenticated users.
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.0.0, < 9.0.10>= 9.1.0, < 9.1.5>= 9.2.0, < 9.2.2>= 9.1.2308, <= 9.1.2308.207>= 9.1.2312, < 9.1.2312.200CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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.
-
Check Splunk Enterprise versionNavigate to Settings > About > Version in Splunk Web, or read the $SPLUNK_HOME/etc/splunk.version file on the serverAffected if Version is 9.0.0 through 9.0.9, 9.1.0 through 9.1.4, or 9.2.0 through 9.2.1 (9.2.2 is fixed)
-
Check Splunk Cloud Platform versionLocate the version information in the Splunk Cloud administration console or cloud instance metadataAffected if Version is 9.1.2308.0 through 9.1.2308.207, or 9.1.2312.0 through 9.1.2312.199 (fixed versions are 9.1.2312.200 and 9.1.2308.207)
-
Verify if Bulletin Messages feature is accessibleCheck if low-privileged users can access Splunk Web Bulletin Messages or create/edit Views by reviewing user role capabilities in Settings > Users and RolesAffected if Users with non-admin/non-power roles have permissions to create or modify Bulletin Messages or custom Views
-
Inspect existing Views and Bulletin Messages for suspicious contentReview saved Views in the Views management interface and check for any Bulletin Messages via the messaging subsystem for injected script tags, javascript: URIs, or event handlersAffected if Any View or Bulletin Message contains unescaped HTML or JavaScript code such as <script>, javascript:, or onload/onerror event handlers
A user is affected if their Splunk version is within the vulnerable ranges AND low-privileged users can access the Bulletin Messages or Views feature, or if malicious script content already exists in Views or Messages.
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 later, and Splunk Cloud Platform to versions 9.1.2312.200 or 9.1.2308.207 or later. As a temporary mitigation, restrict or disable the Bulletin Messages feature and audit existing views and messages for malicious content.
Splunk Enterprise: 9.0.10+, 9.1.5+, or 9.2.2+ | Splunk Cloud Platform: 9.1.2312.200+ or 9.1.2308.207+
- Identify currently running Splunk Enterprise version using $SPLUNK_HOME/bin/splunk version
- 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 9.1.2308.x: Upgrade to version 9.1.2308.207 or later
- For Splunk Cloud Platform 9.1.2312.x: Upgrade to version 9.1.2312.200 or later
- After upgrade, verify the Splunk Web service is running and users can authenticate normally
- Review Splunk Web Bulletin Messages and custom Views for any unauthorized content that may have been injected
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.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,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-36994 — 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-36994 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