Splunk Vulnerabilities

Timeline

The analysis of the timeline helps to identify the required approach and handling of single vulnerabilities and vulnerability collections. This overview makes it possible to see less important slices and more severe hotspots at a glance. Initiating immediate vulnerability response and prioritizing of issues is possible.

Type

The moderation team is working with the threat intelligence team to categorize software that is affected by security vulnerabilities. This helps to illustrate the assignment of these categories to determine the most affected software types.

Product

Splunk Enterprise98
Splunk Cloud Platform22
Splunk Cloud5
Splunk Lite4
Splunk Add-on Builder3

Grouping vulnerabilities by products helps to get an overview. This makes it possible to determine an homogeneous landscape or the most important hotspots in heterogeneous landscapes.

Remediation

Official Fix110
Temporary Fix0
Workaround0
Unavailable0
Not Defined3

Vendors and researchers are eager to find countermeasures to mitigate security vulnerabilities. These can be distinguished between multiple forms and levels of remediation which influence risks differently.

Exploitability

High4
Functional0
Proof-of-Concept2
Unproven0
Not Defined107

Researcher and attacker which are looking for security vulnerabilities try to exploit them for academic purposes or personal gain. The level and quality of exploitability can be distinguished to determine simplicity and strength of attacks.

Access Vector

Not Defined0
Physical0
Local11
Adjacent0
Network102

The approach a vulnerability it becomes important to use the expected access vector. This is typically via the network, local, or physically even.

Authentication

Not Defined0
High13
Low61
None39

To exploit a vulnerability a certail level of authentication might be required. Vulnerabilities without such a requirement are much more popular.

User Interaction

Not Defined0
Required43
None70

Some attack scenarios require some user interaction by a victim. This is typical for phishing, social engineering and cross site scripting attacks.

C3BM Index

Our unique C3BM Index (CVSSv3 Base Meta Index) cumulates the CVSSv3 Meta Base Scores of all entries over time. Comparing this index to the amount of disclosed vulnerabilities helps to pinpoint the most important events.

CVSSv3 Base

≤10
≤20
≤31
≤49
≤522
≤623
≤729
≤820
≤98
≤101

The Common Vulnerability Scoring System (CVSS) is an industry standard to define the characteristics and impacts of security vulnerabilities. The base score represents the intrinsic aspects that are constant over time and across user environments. Our unique meta score merges all available scores from different sources to aggregate to the most reliable result.

CVSSv3 Temp

≤10
≤20
≤31
≤49
≤522
≤628
≤728
≤816
≤99
≤100

The Common Vulnerability Scoring System (CVSS) uses temp scores to reflect the characteristics of a vulnerability that may change over time but not across user environments. This includes reporting confidence, exploitability and remediation levels. We do also provide our unique meta score for temp scores, even though other sources rarely publish them.

VulDB

≤10
≤21
≤311
≤417
≤523
≤623
≤725
≤87
≤96
≤100

The moderation team is always defining the base vector and base score for an entry. These and all other available scores are used to generate the meta score.

NVD

≤10
≤20
≤30
≤42
≤55
≤67
≤713
≤89
≤910
≤104

The National Vulnerability Database (NVD) is also defining CVSS vectors and scores. These are usually not complete and might differ from VulDB scores.

CNA

≤10
≤20
≤32
≤41
≤516
≤69
≤713
≤821
≤928
≤100

A CVE Numbering Authority (CNA) is responsible for assigning new CVE entries. They might also include a CVSS score. These are usually not complete and might differ from VulDB scores.

Vendor

≤10
≤20
≤30
≤40
≤50
≤60
≤70
≤80
≤90
≤100

Some vendors are willing to publish their own CVSS vectors and scores for vulnerabilities in their products. The coverage varies from vendor to vendor.

Research

≤10
≤20
≤30
≤40
≤50
≤60
≤70
≤80
≤90
≤100

There are sometimes also security researcher which provide their own CVSS vectors and scores for vulnerabilities they have found and published.

Exploit 0-day

<1k21
<2k76
<5k16
<10k0
<25k0
<50k0
<100k0
≥100k0

The moderation team is working with the threat intelligence team to determine prices for exploits. Our unique algorithm is used to identify the 0-day prices for an exploit, before it got distributed or became public. Calculated prices are aligned to prices disclosed by vulnerability broker and compared to prices we see on exploit markets.

Exploit Today

<1k113
<2k0
<5k0
<10k0
<25k0
<50k0
<100k0
≥100k0

The 0-day prices do not consider time-relevant factors. The today price does reflect price impacts like disclosure of vulnerability details, alternative exploits, availability of countermeasures. These dynamic aspects might decrease the exploit prices over time. Under certain circumstances this happens very fast.

Exploit Market Volume

Our unique calculation of exploit prices makes it possible to forecast the expected exploit market volume. The calculated prices for all possible 0-day expoits are cumulated for this task. Comparing the volume to the amount of disclosed vulnerabilities helps to pinpoint the most important events.

🔴 CTI Activities

Our unique Cyber Threat Intelligence aims to determine the ongoing research of actors to anticipiate their acitivities. Observing exploit markets on the Darknet, discussions of vulnerabilities on mailinglists, and exchanges on social media makes it possible to identify planned attacks. Monitored actors and activities are classified whether they are offensive or defensive. They are also weighted as some actors are well-known for certain products and technologies. And some of their disclosures might contain more or less details about technical aspects and personal context. The world map highlights active actors in real-time.

Affected Products (17): Add-on Builder (3), App for Lookup File Editing (2), App for Stream (1), Cloud (5), CloudConnect SDK (1), Cloud Platform (22), Enterprise (98), Enterprise Security (2), Enterprise Server (1), Hadoop Connect App (1), IT Service Intelligence (1), Light (2), Lite (4), SOAR (1), Splunk Enterprise (1), Universal Forwarders (1), Web (1)

PublishedBaseTempVulnerabilityProdExpRemEPSSCTICVE
07/01/20245.25.2Splunk Enterprise/Cloud Platform conf-web Settings REST Endpoint cross site scriptingLog Management SoftwareNot DefinedOfficial Fix0.000430.06CVE-2024-36997
07/01/20244.44.4Splunk Enterprise/Cloud Platform cross site scriptingLog Management SoftwareNot DefinedOfficial Fix0.000430.06CVE-2024-36992
07/01/20244.44.4Splunk Enterprise/Cloud Platform Web Bulletin Message cross site scriptingLog Management SoftwareNot DefinedOfficial Fix0.000430.00CVE-2024-36994
07/01/20245.95.7Splunk Enterprise/Cloud Platform authorizationLog Management SoftwareNot DefinedOfficial Fix0.000430.05CVE-2024-36995
07/01/20244.44.4Splunk Enterprise/Cloud Platform Bulletin Message cross site scriptingLog Management SoftwareNot DefinedOfficial Fix0.000430.05CVE-2024-36993
07/01/20246.86.7Splunk Enterprise path traversalLog Management SoftwareNot DefinedOfficial Fix0.109250.03CVE-2024-36991
07/01/20246.56.3Splunk Enterprise/Cloud Platform Datamodel Web REST Endpoint infinite loopLog Management SoftwareNot DefinedOfficial Fix0.000430.05CVE-2024-36990
07/01/20246.76.5Splunk Enterprise/Cloud Platform Notifications access controlLog Management SoftwareNot DefinedOfficial Fix0.000430.00CVE-2024-36989
07/01/20244.34.2Splunk Enterprise/Cloud Platform Indexing Preview REST Endpoint unrestricted uploadLog Management SoftwareNot DefinedOfficial Fix0.000430.05CVE-2024-36987
07/01/20245.95.8Splunk Enterprise/Cloud Platform SPL Safeguard access controlLog Management SoftwareNot DefinedOfficial Fix0.000430.00CVE-2024-36986
07/01/20248.88.6Splunk Enterprise Query deserializationLog Management SoftwareNot DefinedOfficial Fix0.000430.03CVE-2024-36984
07/01/20245.35.2Splunk Enterprise/Cloud Platform observable response discrepancyLog Management SoftwareNot DefinedOfficial Fix0.000430.07CVE-2024-36996
07/01/20248.48.2Splunk Enterprise/Cloud Platform command injectionLog Management SoftwareNot DefinedOfficial Fix0.000430.00CVE-2024-36983
07/01/20246.46.3Splunk Enterprise/Cloud Platform Cluster Config REST Endpoint null pointer dereferenceLog Management SoftwareNot DefinedOfficial Fix0.000430.05CVE-2024-36982
07/01/20248.88.6Splunk Enterprise Splunk_archiver unknown vulnerabilityLog Management SoftwareNot DefinedOfficial Fix0.000430.04CVE-2024-36985
03/27/20247.27.0Splunk Enterprise Dashboard Studio App input validationLog Management SoftwareNot DefinedOfficial Fix0.001250.03CVE-2024-29946
03/27/20244.94.9Splunk Enterprise JsonWebToken Component log fileLog Management SoftwareNot DefinedOfficial Fix0.000500.03CVE-2024-29945
01/30/20245.35.2Splunk Add-on Builder log fileLog Management SoftwareNot DefinedOfficial Fix0.000490.04CVE-2023-46230
01/30/20245.65.5Splunk Add-on Builder Session Token log fileLog Management SoftwareNot DefinedOfficial Fix0.000500.05CVE-2023-46231
01/22/20244.64.6Splunk Enterprise/Cloud RapidDiag Utility log fileLog Management SoftwareNot DefinedOfficial Fix0.000460.04CVE-2024-23677
01/22/20245.95.8Splunk Enterprise/Cloud KV Store access controlLog Management SoftwareNot DefinedOfficial Fix0.000460.04CVE-2024-23675
01/22/20247.77.6Splunk Enterprise deserializationLog Management SoftwareNot DefinedOfficial Fix0.000460.07CVE-2024-23678
01/22/20243.93.8Splunk Enterprise/Cloud SPL Command information disclosureLog Management SoftwareNot DefinedOfficial Fix0.000450.05CVE-2024-23676
01/09/20245.45.3Splunk Enterprise Security Investigation denial of serviceLog Management SoftwareNot DefinedOfficial Fix0.000440.00CVE-2024-22165
01/09/20244.34.2Splunk Enterprise Security Attachment Endpoint resource consumptionLog Management SoftwareNot DefinedOfficial Fix0.000440.06CVE-2024-22164

88 more entries are not shown

Might our Artificial Intelligence support you?

Check our Alexa App!