CyberSecBulletin
CVE-2023-22941NVD status: Modified

Splunk Enterprise: Uncaught Exception

Published Updated By the CyberSecBulletin desk

CVE-2023-22941 is a high-severity uncaught exception vulnerability in Splunk Enterprise from Splunk, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists versions 8.1.13, 8.2.10, 9.0.4 as the first without the flaw, so updating Splunk Enterprise to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 1.03% chance of exploitation within 30 days, higher than 64% of scored CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Splunk Enterprise to 8.1.13 or 8.2.10 or 9.0.4, whichever matches your release line, or a later version.
  2. Update Splunk Cloud Platform to 9.0.2212 or a later version.
  3. Update Splunk to 8.1.13 or 8.2.10 or 9.0.4, whichever matches your release line, or a later version.
  4. Read the advisory on advisory.splunk.com for workarounds and exact fixed builds.
  5. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
SplunkSplunk Enterprise8.1 up to, but not including, 8.1.13; 8.2 up to, but not including, 8.2.10; 9.0 up to, but not including, 9.0.48.1.13, 8.2.10, 9.0.4
SplunkSplunk Cloud Platformbefore 9.0.22129.0.2212
SplunkSplunk8.1.0 up to, but not including, 8.1.13; 8.2.0 up to, but not including, 8.2.10; 9.0.0 up to, but not including, 9.0.48.1.13, 8.2.10, 9.0.4

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
NoneNo data is disclosed.
Integrity
NoneNothing can be modified.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 3.16.5MediumCNA (splunk.com)
CVSS 3.17.5HighNVD

Official description

In Splunk Enterprise versions below 8.1.13, 8.2.10, and 9.0.4, an improperly-formatted ‘INGEST_EVAL’ parameter in a Field Transformation crashes the Splunk daemon (splunkd).

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Uncaught Exception

An exception is thrown from a function, but it is not caught.

How developers prevent this class of flaw

  • The choice between a language which has named or unnamed exceptions needs to be done. While unnamed exceptions exacerbate the chance of not properly dealing with an exception, named exceptions suffer from the up call version of the weak base class problem.
  • A language can be used which requires, at compile time, to catch all serious exceptions. However, one must make sure to use the most current version of the API as new exceptions could be added.
  • Catch all relevant exceptions. This is the recommended solution. Ensure that all exceptions are handled in such a way that you can be sure of the state of your system at any given moment.

More Uncaught Exception vulnerabilities (CWE-248)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
  3. Record last changed materially (score, affected products, status or references).

References

Other vulnerabilities in Splunk Enterprise

All Splunk Enterprise vulnerabilities

Recent Uncaught Exception vulnerabilities

Spotted an error? Tell us.