CVE-2023-46230VulnerabilityPublished 30 Jan 2024Updated 30 May 2025

CVE-2023-46230: Splunk Add-on Builder · Information written to log files can be of a sensitive nature and give valuable guidance to an attacker or expose sensitive user information.

Affects Splunk Add-on BuilderSource CVE Database V5

Not known to be exploited · CVSS 8.2 High : upgrade to 4.1.4 soon.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

8.2High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 32% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 4.1.4

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:L/A:L

Attack Vector: Network
Attack Complexity: Low
Privileges Required: High
User Interaction: None
Scope: Changed
Confidentiality: High
Integrity: Low
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 30 Jan 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Splunk Add-on Builder to 4.1.4.

Affected software

Product	Affected	Fixed in
Splunk Splunk Add-on Builder	Affected <4.1.4	Fixed in 4.1.4

AI-suggested

European organizations should prioritize upgrading the Splunk Add-on Builder to version 4.1.4 or later, where this vulnerability is addressed. Until patching is possible, organizations should implement strict access controls on log files, ensuring that only authorized personnel and systems can read or modify them. Encrypting log storage and transmissions can reduce the risk of unauthorized access. Organizations should audit their current logging configurations to identify and minimize the logging of sensitive information where feasible. Implementing robust monitoring and alerting on access to log files can help detect potential exploitation attempts. Additionally, reviewing and limiting the number of users with high privileges in Splunk environments reduces the attack surface. Employing network segmentation and zero-trust principles around Splunk infrastructure can further contain potential breaches. Finally, organizations should conduct regular security assessments and penetration tests focusing on log management and access controls to identify and remediate weaknesses proactively.

Description

In Splunk Add-on Builder versions below 4.1.4, the app writes sensitive information to internal log files.

Impact

For European organizations, the exposure of sensitive information in Splunk Add-on Builder logs can have severe consequences. Many enterprises and public sector entities across Europe rely on Splunk for security information and event management (SIEM) and operational intelligence. The leakage of sensitive data could lead to unauthorized access to internal systems, data breaches, or compliance violations under regulations such as GDPR. Confidentiality breaches could expose personal data or intellectual property, leading to financial penalties and reputational damage. The vulnerability’s requirement for high privileges means that attackers would likely need to have already compromised an account with elevated rights, but once exploited, the attacker could gain further footholds or escalate privileges. This risk is particularly critical for organizations handling sensitive personal data, critical infrastructure, or financial information. Additionally, the exposure of sensitive logs could aid attackers in crafting more effective attacks or evading detection, undermining the overall security posture of affected organizations.

References

advisory.splunk.com/advisories/SVD-2024-0111 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 8 Jul 2025, 14:26 UTC

Technical details

References

Community reviews

Related threats