# CVE-2023-46231: Session Token Disclosure to Internal Log Files in Splunk Add-on Builder

> Attackers with log access can steal session tokens from Splunk Add-on Builder logs, potentially leading to account takeover.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 30 Jan 2024
- **Updated:** 28 Feb 2025
- **Also known as:** GHSA-g78p-m98v-8prx

## What is CVE-2023-46231?

CVE-2023-46231 is a high-severity vulnerability in Splunk Add-on Builder, published on 30 Jan 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### 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.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

## Which versions are affected by CVE-2023-46231?

It affects 1 product.


Products: Splunk Add-on Builder.

## How do I fix CVE-2023-46231?

No fix has been published for CVE-2023-46231 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-46231 being exploited?

There is no known exploitation of CVE-2023-46231 in the wild and no public exploit code.

## Other vulnerabilities in Splunk Add-on Builder

- [CVE-2023-46230](https://insights.sbomify.com/CVE-2023-46230/): Sensitive Information Disclosure to Internal Log Files in Splunk Add-on Builder (high 8.2)
- [CVE-2023-22943](https://insights.sbomify.com/CVE-2023-22943/): Security feature bypass in Splunk Add-on Builder (medium 4.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-46231 and fix it if it is affected.

What it is: CVE-2023-46231 is a high-severity vulnerability in Splunk Add-on Builder, published on 30 Jan 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-46231 in the wild and no public exploit code.

Affected product: Splunk Add-on Builder. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-46231/ (Markdown: https://insights.sbomify.com/CVE-2023-46231/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-46231
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-46231
- OSV: https://osv.dev/vulnerability/CVE-2023-46231

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-46231/
Summaries are generated and may contain mistakes; the official description above is the record.