dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2024-53247

HIGH · 8.8 CVSS v3.1 Published 2024-12-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
In Splunk Enterprise versions below 9.3.2, 9.2.4, and 9.1.7, and versions below 3.4.261 and 3.7.13 of the Splunk Secure Gateway app on Splunk Cloud Platform, a low-privileged user that does not hold the “admin“ or “power“ Splunk roles could perform a Remote Code Execution (RCE).

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 confidence

A privilege escalation vulnerability in Splunk Enterprise and the Splunk Secure Gateway app allows low-privileged users (without admin or power roles) to execute arbitrary code remotely. The flaw enables a standard user to bypass authorization controls and achieve RCE, likely through improper validation of user privileges in certain endpoints or functionalities.

MitigationUpgrade Splunk Enterprise to versions 9.3.2, 9.2.4, or 9.1.7 and later, or upgrade the Splunk Secure Gateway app to version 3.4.261, 3.7.13 or later for Splunk Cloud Platform.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS 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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Splunk Enterprise version
    Run: splunk version or check $SPLUNK_HOME/etc/splunk.version file
    Affected if Version is 9.3.0-9.3.1, 9.2.0-9.2.3, 9.1.0-9.1.6, or any earlier 9.x release before 9.1.7/9.2.4/9.3.2
  2. Identify installed Splunk Secure Gateway app version
    Navigate to Apps > Manage Apps in Splunk Web, or check $SPLUNK_HOME/etc/apps/splunk_secure_gateway/default/app.conf for version
    Affected if Version is below 3.4.261 or 3.7.13 (or if version cannot be determined but the app is present)
  3. Confirm Splunk Secure Gateway app is installed and enabled
    Check for splunk_secure_gateway in $SPLUNK_HOME/etc/apps/ directory or via Splunk Web Apps management interface
    Affected if The app is installed and enabled in the environment
  4. Identify presence of low-privileged non-admin users
    Run: | rest /services/authentication/users | search roles!=admin roles!=power OR check Splunk Web > Settings > Users and Roles
    Affected if Standard or low-privileged users exist who lack admin or power roles
  5. Verify if remote access or API endpoints are exposed for low-privileged users
    Review Splunk Secure Gateway configuration and access controls; check for exposed endpoints that standard users can access via web or API
    Affected if Splunk Secure Gateway endpoints are accessible to standard (non-admin, non-power) users

Your environment is affected if Splunk Enterprise is below version 9.1.7/9.2.4/9.3.2 OR Splunk Secure Gateway app is below 3.4.261/3.7.13, AND low-privileged users exist with access to the Splunk Secure Gateway functionality.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Splunk Enterprise to versions 9.3.2, 9.2.4, or 9.1.7 and later, or upgrade the Splunk Secure Gateway app to version 3.4.261, 3.7.13 or later for Splunk Cloud Platform.

Recommended fix High confidence

Splunk Enterprise 9.3.2, 9.2.4, or 9.1.7; Splunk Secure Gateway app 3.4.261 or 3.7.13

  1. Identify your current Splunk Enterprise version by navigating to Settings > About > Version information
  2. If running Splunk Enterprise, upgrade to version 9.3.2, 9.2.4, or 9.1.7 depending on your current branch (upgrade to the latest in your branch)
  3. If using Splunk Secure Gateway app on Splunk Cloud Platform, upgrade the app to version 3.4.261 or 3.7.13
  4. After upgrade, verify the version change was successful in About > Version information
  5. Test that the low-privileged user no longer has the ability to perform deserialization attacks

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,928.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-53247 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-53247 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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