CVE-2024-29945
Splunk Authentication Token Exposure in Debug Log in Splunk Enterprise
Description
In Splunk Enterprise versions below 9.2.1, 9.1.4, and 9.0.9, the software potentially exposes authentication tokens during the token validation process. This exposure happens when either Splunk Enterprise runs in debug mode or the JsonWebToken component has been configured to log its activity at the DEBUG logging level.
INFO
Published Date :
March 27, 2024, 5:15 p.m.
Last Modified :
Nov. 21, 2024, 9:08 a.m.
Remotely Exploit :
Yes !
Source :
[email protected]
CVSS Scores
Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
---|---|---|---|---|---|---|
CVSS 3.1 | HIGH | [email protected] | ||||
CVSS 3.1 | HIGH | [email protected] |
Solution
- There are multiple solutions depending on how you have configured the Splunk Enterprise instance.First, determine whether or not debug logging is on, either globally or for the JsonWebToken component. You must log into the Splunk Enterprise instance as an admin user or equivalent to perform these actions.To determine the current global logging mode on the instance:In a web browser, visit the Server Logging Settings page in Splunk Web at /en- US/manager/system/server/logger.Review the Logging Level column on the page that loads. If every row in this column shows DEBUG as the logging level, then the Splunk Enterprise instance is in debug mode. Otherwise, it is not in debug mode.To determine the current logging level for the JsonWebToken processor:In a web browser, search for the JsonWebToken processor configuration by visiting /en-US/manager/system/server/logger?search=JsonWebToken.Review the Logging level column for the processor. If this row has a value of DEBUG, then the processor currently logs its activity at the DEBUG level.See Enable debug logging for more information.If either of these steps determines that debug logging is on, either globally or for the JsonWebToken component, then remedy the problem by performing the following tasks:Upgrade Splunk Enterprise to versions 9.2.1, 9.1.4, 9.0.9, or higher.Delete the following log file on the Splunk Enterprise instance: $SPLUNK_HOME/var/log/splunk/splunkd.logLog into Splunk Web on the Splunk Enterprise instance and delete all log file events for the JsonWebToken component from the _internal index by running the following search command: index=_internal component=JsonWebToken | deleteNote: The delete SPL command requires the can_delete role, which administrators do not receive by default. See delete for more info on the delete search command.While you are logged in, rotate any potentially exposed authentication tokens. See Manage or delete authentication tokens for more information.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2024-29945
.
URL | Resource |
---|---|
https://advisory.splunk.com/advisories/SVD-2024-0301 | Mitigation Vendor Advisory |
https://research.splunk.com/application/9a67e749-d291-40dd-8376-d422e7ecf8b5 | Technical Description Vendor Advisory |
https://advisory.splunk.com/advisories/SVD-2024-0301 | Mitigation Vendor Advisory |
https://research.splunk.com/application/9a67e749-d291-40dd-8376-d422e7ecf8b5 | Technical Description Vendor Advisory |
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2024-29945
is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2024-29945
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2024-29945
vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2024-29945
vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Modified by af854a3a-2127-422b-91ae-364da2661108
Nov. 21, 2024
Action Type Old Value New Value Added Reference https://advisory.splunk.com/advisories/SVD-2024-0301 Added Reference https://research.splunk.com/application/9a67e749-d291-40dd-8376-d422e7ecf8b5 -
CVE Modified by [email protected]
May. 14, 2024
Action Type Old Value New Value -
CVE Modified by [email protected]
Apr. 10, 2024
Action Type Old Value New Value -
Initial Analysis by [email protected]
Apr. 01, 2024
Action Type Old Value New Value Added CVSS V3.1 NIST AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H Changed Reference Type https://advisory.splunk.com/advisories/SVD-2024-0301 No Types Assigned https://advisory.splunk.com/advisories/SVD-2024-0301 Mitigation, Vendor Advisory Changed Reference Type https://research.splunk.com/application/9a67e749-d291-40dd-8376-d422e7ecf8b5 No Types Assigned https://research.splunk.com/application/9a67e749-d291-40dd-8376-d422e7ecf8b5 Technical Description, Vendor Advisory Added CWE NIST CWE-532 Added CPE Configuration OR *cpe:2.3:a:splunk:splunk:*:*:*:*:enterprise:*:*:* versions from (including) 9.0.0 up to (excluding) 9.0.9 *cpe:2.3:a:splunk:splunk:*:*:*:*:enterprise:*:*:* versions from (including) 9.1.0 up to (excluding) 9.1.4 *cpe:2.3:a:splunk:splunk:*:*:*:*:enterprise:*:*:* versions from (including) 9.2.0 up to (excluding) 9.2.1 -
CVE Modified by [email protected]
Mar. 27, 2024
Action Type Old Value New Value Added Reference Splunk Inc. https://research.splunk.com/application/9a67e749-d291-40dd-8376-d422e7ecf8b5 [No types assigned] -
CVE Received by [email protected]
Mar. 27, 2024
Action Type Old Value New Value Added Description In Splunk Enterprise versions below 9.2.1, 9.1.4, and 9.0.9, the software potentially exposes authentication tokens during the token validation process. This exposure happens when either Splunk Enterprise runs in debug mode or the JsonWebToken component has been configured to log its activity at the DEBUG logging level. Added Reference Splunk Inc. https://advisory.splunk.com/advisories/SVD-2024-0301 [No types assigned] Added CWE Splunk Inc. CWE-532 Added CVSS V3.1 Splunk Inc. AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H