CyberSecBulletin
CVE-2023-46231NVD status: Modified

Splunk Add-on Builder: Insertion of Sensitive Information into Log File

CVE-2023-46231 is a high-severity insertion of sensitive information into log file vulnerability in Splunk Add-on Builder from Splunk, with a CVSS 3.1 base score of 7.2 out of 10. It can be exploited remotely over the network by an attacker with administrator privileges, without any action from a user. The record lists version 4.1.4 as the first without the flaw, so updating Splunk Add-on Builder to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.48% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Splunk Add-on Builder to 4.1.4 or a later version.
  2. Update Add-on Builder to 4.1.4 or a later version.
  3. Read the advisory on advisory.splunk.com for workarounds and exact fixed builds.

Affected products and versions

VendorProductAffected versionsFixed in
SplunkSplunk Add-on Builderbefore 4.1.44.1.4
SplunkAdd-on Builderbefore 4.1.44.1.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
HighAdministrator-level access is required first.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

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

Scoring systemScoreSeverityScored by
CVSS 3.16.8MediumCNA (splunk.com)
CVSS 3.17.2HighNVD

Official description

In Splunk Add-on Builder versions below 4.1.4, the application writes user session tokens to its internal log files when you visit the Splunk Add-on Builder or when you build or edit a custom app or add-on.

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

The underlying weakness: Insertion of Sensitive Information into Log File

The product writes sensitive information to a log file.

How developers prevent this class of flaw

  • Consider seriously the sensitivity of the information written into log files. Do not write secrets into the log files.
  • Remove debug log files before deploying the application into production.
  • Protect log files against unauthorized read/write.

More Insertion of Sensitive Information into Log File vulnerabilities (CWE-532)

Timeline

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

References

Recent Insertion of Sensitive Information into Log File vulnerabilities

Spotted an error? Tell us.