CVE-2025-20384
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 Enterprise versions below 10.0.1, 9.4.6, 9.3.8, and 9.2.10, and Splunk Cloud Platform versions below 10.1.2507.4, 10.0.2503.6, and 9.3.2411.117.125, an unauthenticated attacker can inject American National Standards Institute (ANSI) escape codes into Splunk log files due to improper validation at the /en-US/static/ web endpoint. This may allow them to poison, forge, or obfuscate sensitive log data through specially crafted HTTP requests, potentially impacting log integrity and detection capabilities.
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 confidenceThis is an input validation vulnerability in Splunk Enterprise and Cloud Platform where the /en-US/static/ web endpoint fails to properly sanitize ANSI escape codes from HTTP requests. An unauthenticated remote attacker can inject malicious ANSI sequences that poison or obfuscate log entries, compromising log integrity and potentially bypassing security monitoring.
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>= 9.2.0, < 9.2.10>= 9.3.0, < 9.3.8>= 9.4.0, < 9.4.6= 10.0.0>= 9.3.2411, < 9.3.2411.117>= 10.0.2503, < 10.0.2503.6>= 10.1.2507, < 10.1.2507.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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
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.
-
Identify Splunk product and versionRun 'splunk version' from the Splunk installation bin directory, or check the $SPLUNK_HOME/etc/splunk.version fileAffected if The installed version falls within these ranges: Splunk Enterprise 9.2.0 to 9.2.9, 9.3.0 to 9.3.7, 9.4.0 to 9.4.5, or exactly 10.0.0; Splunk Cloud Platform 9.3.2411 to 9.3.2411.116, 10.0.2503 to 10.0.2503.5, or 10.1.2507 to 10.1.2507.3
-
Verify Splunk Web service is enabledCheck the web.conf configuration file in $SPLUNK_HOME/etc/system/local/ for the 'enableSplunkWeb' setting, or verify port 8000 is listening with 'netstat -an | grep 8000'Affected if Splunk Web is running and the /en-US/ endpoint is accessible on port 8000 (or configured alternative port)
-
Confirm the /en-US/static/ endpoint is reachableSend a request to http://<splunk_host>:8000/en-US/static/ and verify a response is receivedAffected if The endpoint returns HTTP 200 or another successful response, indicating it is accessible to unauthenticated users
-
Inspect HTTP request handling for the static endpointReview Splunk access logs in $SPLUNK_HOME/var/log/splunk/web_access.log for requests to /en-US/static/ paths and check if the web server processes these without filteringAffected if The server processes requests to /en-US/static/ and logs them without stripping ANSI escape sequences
A user is affected if they run a vulnerable Splunk Enterprise or Cloud Platform version with Splunk Web enabled, making the /en-US/static/ endpoint accessible to unauthenticated attackers who can inject ANSI escape codes into logs.
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 · scoped9.2.109.3.89.3.2411.117
Upgrade Splunk to version 10.0.1+, 9.4.6+, 9.3.8+, 9.2.10+ (Enterprise) or 10.1.2507.4+, 10.0.2503.6+, 9.3.2411.117.125+ (Cloud Platform). Alternatively, implement web application firewall rules to block requests containing ANSI escape sequences at the /en-US/static/ endpoint.
Splunk Enterprise: 9.2.10, 9.3.8, 9.4.6, or 10.0.1 (or later); Splunk Cloud Platform: 9.3.2411.117, 10.0.2503.6, or 10.1.2507.4 (or later)
- Identify the current Splunk Enterprise or Splunk Cloud Platform version running in your environment
- Determine the appropriate upgrade path based on your current version (9.2.x -> 9.2.10+, 9.3.x -> 9.3.8+, 9.4.x -> 9.4.6+, 10.0.x -> 10.0.1+)
- Review Splunk upgrade documentation and release notes for the target version
- Schedule upgrade during a planned maintenance window
- For Splunk Enterprise: Download and install the fixed version from splunk.com
- For Splunk Cloud Platform: Contact Splunk Support to request the patched version
- After upgrade, verify the /en-US/static/ endpoint no longer accepts ANSI escape sequences
- Validate log integrity by reviewing log files for proper formatting
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,416.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-20384 — 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-2025-20384 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