CVE-2024-53244
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.2.2406.107, 9.2.2403.109, and 9.1.2312.206, a low-privileged user that does not hold the “admin“ or “power“ Splunk roles could run a saved search with a risky command using the permissions of a higher-privileged user to bypass the SPL safeguards for risky commands on “/en-US/app/search/report“ endpoint through “s“ parameter.<br>The vulnerability requires the attacker to phish the victim by tricking them into initiating a request within their browser. The authenticated user should not be able to exploit the vulnerability at will.
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 confidenceThis is a privilege escalation and SPL safeguards bypass vulnerability in Splunk Enterprise and Cloud Platform. A low-privileged user (non-admin, non-power role) can exploit the 's' parameter on the /en-US/app/search/report endpoint to run saved searches with the permissions of a higher-privileged user, effectively bypassing SPL safeguards that restrict risky commands. The attack requires social engineering to trick a victim into initiating a malicious request.
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.109>= 9.2.2406, < 9.2.2406.107CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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 versionNavigate to Settings > About > About Splunk, or run the command: splunk versionAffected if Version is 9.1.0 through 9.1.6, 9.2.0 through 9.2.3, or 9.3.0 through 9.3.1 (not yet patched)
-
Check Splunk Cloud Platform versionIn Splunk Cloud, check the version displayed in the system banner or contact Splunk Cloud support for version confirmationAffected if Version is 9.1.2312 through 9.1.2312.205, 9.2.2403 through 9.2.2403.108, or 9.2.2406 through 9.2.2406.106 (not yet patched)
-
Review audit logs for the vulnerable endpointSearch audit logs for requests to /en-US/app/search/report with the 's' parameter: index=_audit action=search (savedsearches) | where uri contains "app/search/report" and uri contains "s="Affected if Requests found where a low-privileged user accessed saved searches belonging to higher-privileged users via the 's' parameter
-
Examine saved search execution patternsSearch the _internal index for saved search executions: index=_internal sourcetype=splunkd savedsearch_name=* | stats count by user savedsearch_nameAffected if A non-admin user executed saved searches belonging to admin or power roles that they should not normally have access to
You are affected if your Splunk version falls within any of the affected ranges AND audit logs show evidence of the /en-US/app/search/report endpoint being exploited with the 's' parameter to bypass SPL safeguards.
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 Enterprise to versions 9.3.2, 9.2.4, or 9.1.7 (or higher), and Splunk Cloud Platform to versions 9.2.2406.107, 9.2.2403.109, or 9.1.2312.206 (or higher). Additionally, educate users about phishing attacks and implement network-level protections for suspicious requests.
Splunk Enterprise: 9.1.7, 9.2.4, or 9.3.2 (or higher); Splunk Cloud Platform: 9.1.2312.206, 9.2.2403.109, or 9.2.2406.107 (or higher)
- 1. Identify your current Splunk Enterprise or Splunk Cloud Platform version using the 'About Splunk' page in the web interface or the 'splunk version' CLI command
- 2. For Splunk Enterprise: Schedule a maintenance window for the upgrade process
- 3. For Splunk Enterprise: Back up your Splunk configuration directory (typically $SPLUNK_HOME/etc/)
- 4. For Splunk Enterprise: Download the appropriate fixed version installer from splunk.com/download
- 5. For Splunk Cloud Platform: Contact Splunk Support or your Splunk Cloud administrator to request the upgrade to the fixed version
- 6. For Splunk Enterprise: Run the installer and follow the standard upgrade procedure
- 7. After upgrade, verify the Splunk Web interface is accessible and confirm the new version number matches the fixed release
- 8. Test that the vulnerability is remediated by verifying low-privileged users can no longer exploit the /en-US/app/search/report endpoint through the s parameter
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-53244 — 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-53244 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