CVE-2024-53246
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.3.2, 9.2.4, and 9.1.7 and Splunk Cloud Platform versions below 9.3.2408.101, 9.2.2406.106, 9.2.2403.111, and 9.1.2312.206, an SPL command can potentially disclose sensitive information. The vulnerability requires the exploitation of another vulnerability, such as a Risky Commands Bypass, for successful exploitation.
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 · moderate confidenceAn SPL (Search Processing Language) command in Splunk Enterprise below 9.3.2/9.2.4/9.1.7 and Splunk Cloud Platform below 9.3.2408.101/9.2.2406.106/9.2.2403.111/9.1.2312.206 can disclose sensitive information, but only when chained with another vulnerability such as a Risky Commands Bypass.
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.0, < 9.1.7>= 9.2.0, < 9.2.4>= 9.3.0, < 9.3.2>= 9.1.2312, < 9.1.2312.206>= 9.2.2403, < 9.2.2403.111>= 9.2.2406, < 9.2.2406.106>= 9.3.2408, < 9.3.2408.101CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Check Splunk Enterprise versionRun 'splunk --version' from the Splunk bin directory, or log into the web UI and navigate to Settings > Server settings > Server information to view the full version stringAffected if The version is 9.1.0 to 9.1.6.x, 9.2.0 to 9.2.3.x, or 9.3.0 to 9.3.1.x (Enterprise)
-
Check Splunk Cloud Platform versionLog into Splunk Cloud Portal or use the Splunk Cloud API to retrieve the installed version from the deployment informationAffected if The version is 9.1.2312.000 to 9.1.2312.205, 9.2.2403.000 to 9.2.2403.110, 9.2.2406.000 to 9.2.2406.105, or 9.3.2408.000 to 9.3.2408.100 (Cloud Platform)
-
Determine if risky commands bypass vulnerabilities existReview Splunk security advisories for any active Risky Commands Bypass vulnerabilities in your environment, or check Splunk ES correlations for alerts related to command bypass attemptsAffected if A Risky Commands Bypass vulnerability (such as CVE-2024-XXXX) is present and exploitable in the same environment
-
Identify if vulnerable SPL command usage is possibleReview Splunk search logs and audit trails for execution of the affected SPL command (typically related to internal commands that access sensitive data) combined with bypass conditionsAffected if The specific SPL command that can leak sensitive information is being executed in your environment with bypass conditions active
You are affected only if your Splunk version falls within the vulnerable ranges AND a Risky Commands Bypass vulnerability exists in your environment, allowing the SPL command to be chained for information disclosure.
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.1.79.1.2312.2069.2.4
Upgrade Splunk to version 9.3.2, 9.2.4, or 9.1.7 (Enterprise) or the corresponding patched Cloud Platform versions. Additionally, address any vulnerable Risky Commands Bypass flaws to prevent chaining attacks.
Splunk Enterprise: 9.1.7, 9.2.4, or 9.3.2 | Splunk Cloud Platform: 9.1.2312.206, 9.2.2403.111, 9.2.2406.106, or 9.3.2408.101
- Identify your current Splunk Enterprise or Splunk Cloud Platform version
- For Splunk Enterprise: upgrade to version 9.1.7, 9.2.4, or 9.3.2 (or later)
- For Splunk Cloud Platform: upgrade to version 9.1.2312.206, 9.2.2403.111, 9.2.2406.106, or 9.3.2408.101 (or later)
- After upgrade, verify the Splunk services are running correctly
- Confirm the upgrade by checking the Splunk version in the About page
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-53246 — 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-53246 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