dbcve.org
CloudApplication · Splunk

CVE-2024-23675

MEDIUM · 6.5 CVSS v3.1 Published 2024-01-22
Fix available
A fix is available. Upgrade to 9.0.8 / 9.1.3 or later.
See remediation →
71/100
Remediation priority · Elevated
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.0.8 and 9.1.3, Splunk app key value store (KV Store) improperly handles permissions for users that use the REST application programming interface (API). This can potentially result in the deletion of KV Store collections.

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

Splunk Enterprise's KV Store improperly validates permissions for REST API users, allowing authenticated users to delete KV Store collections they should not have access to modify. This authorization bypass affects versions below 9.0.8 and 9.1.3.

MitigationUpgrade Splunk Enterprise to version 9.0.8, 9.1.3, or later to remediate this vulnerability.

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
CloudApplication
Affected:< 9.1.2312.100
SplunkApplication
Affected:>= 9.0.0, < 9.0.8>= 9.1.0, < 9.1.3

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
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 checks

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

  1. Check Splunk Enterprise version
    Navigate to Settings > Server Settings > Server Information, or run the command: splunk --version or check $SPLUNK_HOME/etc/splunk.version
    Affected if The installed version is >= 9.0.0 and < 9.0.8, or >= 9.1.0 and < 9.1.3 (for Enterprise); or < 9.1.2312.100 (for Splunk Cloud)
  2. Identify if KV Store collections exist
    Run the REST API query: | rest /servicesNS/-/search/storage/collections/config spl_server=localhost
    Affected if Any KV Store collections are defined in the environment
  3. Check for REST API users with limited collection permissions
    Review user roles and capabilities in Settings > Users and Authentication > Roles. Look for users with api_enabled set and specific collection-level permissions
    Affected if Any REST API users exist who have access to KV Store but lack full delete permissions on certain collections
  4. Verify KV Store collection permission assignments
    Query collection permissions via: | rest /servicesNS/-/search/storage/collections/manager spl_server=localhost | fields collection allowDelete
    Affected if There are collections where allowDelete is set to a restricted value or differs from the user's expected permissions

You are affected if your Splunk version falls within the vulnerable ranges AND you have KV Store collections in use with REST API users who might bypass intended collection-level delete restrictions.

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
Upgrade available Upgrade to 9.0.8 / 9.1.3 / 9.1.2312.100 or later
Fixed in 9.0.89.1.39.1.2312.100
Interim mitigation

Upgrade Splunk Enterprise to version 9.0.8, 9.1.3, or later to remediate this vulnerability.

Recommended fix High confidence

Splunk Enterprise 9.0.8 (for 9.0.x line) or 9.1.3 (for 9.1.x line); Splunk Cloud 9.1.2312.100

  1. 1. Identify the current Splunk Enterprise version by navigating to Settings > About > Version in the Splunk UI or running 'splunk --version' from the command line.
  2. 2. If running Splunk 9.0.x (versions 9.0.0 through 9.0.7), upgrade to Splunk Enterprise 9.0.8 or later.
  3. 3. If running Splunk 9.1.x (versions 9.1.0 through 9.1.2), upgrade to Splunk Enterprise 9.1.3 or later.
  4. 4. For Splunk Cloud customers, upgrade to version 9.1.2312.100 or later (contact Splunk Support for cloud upgrade assistance).
  5. 5. After upgrading, verify KV Store functionality and review user permissions to ensure the fix is properly applied.
Caveat Standard Splunk upgrade procedures apply - review Splunk documentation for version-specific migration notes and ensure proper backups before upgrading

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

Fix this in Cloud Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-23675 — 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-23675 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