dbcve.org
Enterprise SecurityApplication · Splunk

CVE-2024-22165

MEDIUM · 6.5 CVSS v3.1 Published 2024-01-09
Fix available
A fix is available. Upgrade to 7.1.2 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 Security (ES) versions lower than 7.1.2, an attacker can create a malformed Investigation to perform a denial of service (DoS). The malformed investigation prevents the generation and rendering of the Investigations manager until it is deleted.<br>The vulnerability requires an authenticated session and access to create an Investigation. It only affects the availability of the Investigations manager, but without the manager, the Investigations functionality becomes unusable for most users.

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

In Splunk Enterprise Security versions below 7.1.2, an authenticated user with Investigation creation privileges can create a malformed Investigation object that causes a denial of service. This malformed object corrupts the Investigations manager's ability to generate and render, rendering the entire Investigations feature non-functional for most users until the malformed investigation is manually deleted.

MitigationUpgrade Splunk Enterprise Security to version 7.1.2 or later to remediate this vulnerability. In the interim, monitor for and promptly delete any malformed Investigations that may be causing service disruption.

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
Enterprise SecurityApplication
Affected:>= 7.1.0, < 7.1.2

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
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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. Verify Splunk Enterprise Security version
    Navigate to the Splunk Enterprise Security dashboard, go to Settings > About > Product Info, and locate the Enterprise Security version number. Alternatively, check the etc/apps/splunk_es_appinfo/local/app.conf file for the version field.
    Affected if The version is 7.1.0, 7.1.1, or any version less than 7.1.2 (versions 7.1.0 through 7.1.1 inclusive are affected).
  2. Confirm Investigations feature accessibility
    Attempt to access the Investigations interface in Splunk Enterprise Security. Go to the Enterprise Security dashboard and click on the Investigations tab or navigate to Investigate > Investigation Center.
    Affected if The Investigations page fails to load, displays error messages, or shows that the Investigations manager cannot generate or render objects.
  3. Check for corrupted Investigation objects
    Use Splunk search to query the investigations index or check the internal logs for errors related to the Investigations manager. Search for events containing phrases like 'corrupt', 'malformed', or 'render failed' in the context of investigations.
    Affected if Search results show errors indicating malformed Investigation objects exist or the Investigations manager is unable to process existing investigations.

A user is affected if their Splunk Enterprise Security version is 7.1.0, 7.1.1, or any version below 7.1.2 AND the Investigations feature is non-functional or throwing errors related to malformed objects.

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 7.1.2 or later
Fixed in 7.1.2
Interim mitigation

Upgrade Splunk Enterprise Security to version 7.1.2 or later to remediate this vulnerability. In the interim, monitor for and promptly delete any malformed Investigations that may be causing service disruption.

Recommended fix High confidence

Splunk Enterprise Security 7.1.2

  1. Back up your Splunk Enterprise Security configuration and data before proceeding with the upgrade
  2. Download Splunk Enterprise Security version 7.1.2 from the official Splunk website or your Splunk account
  3. Upgrade your Splunk Enterprise deployment to version 7.1.2 following Splunk's standard upgrade procedures
  4. After upgrade, verify the Investigations manager loads correctly and is fully functional
  5. Confirm that new Investigations can be created, saved, and rendered without errors

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

Fix this in Enterprise Security Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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