Splunk Enterprise up to 9.0.7/9.1.2 on Windows deserialization

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
7.6$0-$5k0.00

Summaryinfo

A vulnerability described as critical has been identified in Splunk Enterprise up to 9.0.7/9.1.2 on Windows. This affects an unknown function. Such manipulation leads to deserialization. This vulnerability is uniquely identified as CVE-2024-23678. Local access is required to approach this attack. No exploit exists. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability, which was classified as critical, has been found in Splunk Enterprise up to 9.0.7/9.1.2 on Windows (Log Management Software). Affected by this issue is an unknown code block. The manipulation with an unknown input leads to a deserialization vulnerability. Using CWE to declare the problem leads to CWE-502. The product deserializes untrusted data without sufficiently verifying that the resulting data will be valid. Impacted is confidentiality, integrity, and availability. CVE summarizes:

In Splunk Enterprise for Windows versions below 9.0.8 and 9.1.3, Splunk Enterprise does not correctly sanitize path input data. This results in the unsafe deserialization of untrusted data from a separate disk partition on the machine. This vulnerability only affects Splunk Enterprise for Windows.

The weakness was disclosed 01/22/2024 as SVD-2024-0108. The advisory is shared for download at advisory.splunk.com. This vulnerability is handled as CVE-2024-23678 since 01/19/2024. Successful exploitation requires user interaction by the victim. There are neither technical details nor an exploit publicly available.

Upgrading to version 9.0.8 or 9.1.3 eliminates this vulnerability.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.7
VulDB Meta Temp Score: 7.6

VulDB Base Score: 6.7
VulDB Temp Score: 6.4
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 8.8
NVD Vector: 🔍

CNA Base Score: 7.5
CNA Vector (Splunk Inc.): 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

Exploitinginfo

Class: Deserialization
CWE: CWE-502 / CWE-20
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: Partially

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: Enterprise 9.0.8/9.1.3

Timelineinfo

01/19/2024 🔍
01/22/2024 +3 days 🔍
01/22/2024 +0 days 🔍
02/16/2024 +25 days 🔍

Sourcesinfo

Advisory: SVD-2024-0108
Status: Confirmed

CVE: CVE-2024-23678 (🔍)
GCVE (CVE): GCVE-0-2024-23678
GCVE (VulDB): GCVE-100-251732

Entryinfo

Created: 01/22/2024 22:43
Updated: 02/16/2024 11:13
Changes: 01/22/2024 22:43 (52), 02/16/2024 11:13 (11)
Complete: 🔍
Cache ID: 216::103

Once again VulDB remains the best source for vulnerability data.

Discussion

 Anonymous User (+0)
2 years ago
Good morning,
Could You please also add the following cpe "splunk:enterprise" since it is Splunk Enterprise?
We would appreciate it very much.
Best regards,
TEAM CERT
 VulDB Community Team2 years ago
Unfortunately, the CPE entry cpe:2.3:a:splunk:enterprise does not exist in the official dictionary. They define it by edition which is currently not supported in VulDB.

◂ PreviousOverviewNext ▸

Might our Artificial Intelligence support you?

Check our Alexa App!