CVE-2023-46231
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Splunk Add-on Builder versions below 4.1.4 contain a vulnerability where user session tokens are written to internal log files during normal operation—specifically when users visit the Add-on Builder interface or create/edit custom apps or add-ons. This exposes session credentials to anyone with access to those log files, potentially allowing session hijacking.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 4.1.4CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Splunk Add-on Builder is installedCheck the Splunk apps directory or use Splunk's web interface to view installed apps. Look for 'Add-on Builder' in the app list.Affected if The Add-on Builder app is present in the Splunk installation.
-
Identify the installed version of Add-on BuilderNavigate to the Splunk web interface, find the Add-on Builder app, and view its version in the app settings or check the app.conf file in the Add-on Builder app directory.Affected if The version is lower than 4.1.4.
-
Locate Splunk internal log filesCheck the default Splunk log directory (typically $SPLUNK_HOME/var/log/splunk/) or review the 'audit.log' and 'web_service.log' files for recent entries.Affected if Log files exist and contain entries from Add-on Builder usage.
-
Inspect logs for session token exposureSearch log files for patterns resembling session tokens, authentication headers, or 'session' keyword combined with user credentials. Use grep or Splunk search to examine logs created during Add-on Builder interface access.Affected if Log files contain session tokens, session IDs, or authentication credentials in plain text.
-
Review Add-on Builder usage historyCheck Splunk audit logs or web access logs for activity related to the Add-on Builder interface (URLs containing '/app/Splunk_TA_solutions' or 'addon_builder') and note if custom apps or add-ons were created or edited.Affected if Users have accessed the Add-on Builder interface or created/edited add-ons since installation.
If the Add-on Builder version is below 4.1.4 and logs from its interface access exist, session tokens may have been written to log files and could be at risk of exposure.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped4.1.4
Upgrade the Splunk Add-on Builder to version 4.1.4 or later to prevent session tokens from being written to log files.
Splunk Add-on Builder 4.1.4
- Download Splunk Add-on Builder version 4.1.4 or later from Splunkbase or the official Splunk repository
- Upgrade the Add-on Builder in your Splunk environment by installing the new version
- Restart the Splunk services if required by the upgrade process
- Verify the upgrade was successful by checking the Add-on Builder version in Splunk Manage Apps
- Review existing log files in $SPLUNK_HOME/var/log/splunk/ for any exposed session tokens and consider rotating sessions
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-46231 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-46231 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data