Cyber Resilience

CVE-2025-20384

Splunk 9.2.0 – 9.2.10

Published
03 December 2025
Modified
05 December 2025
Patch / advisory
View advisory
CVSS Score v3.1 5.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
EPSS Score 0.0039 32th percentile
Risk Priority 44 floored blend · peak EPSS

Summary

CVE-2025-20384 is a medium-severity Improper Output Neutralization for Logs (CWE-117) vulnerability in Splunk Splunk. Its CVSS base score is 5.3 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Indicator Removal (T1070); ranked at the 32th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A09:2025 Security Logging and Alerting Failures

EU & UK References

Vulnerability Data

In 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…

more

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.

CWE(s)
CWE-117

Related Threats

MITRE ATT&CK Enterprise Techniques

T1070 Indicator Removal Stealth
Adversaries may selectively delete or modify artifacts generated to reduce indications of their presence and blend in with legitimate activity.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-20388Same product: Splunk Splunk
CVE-2023-40595Same product: Splunk Splunk
CVE-2025-20382Same product: Splunk Splunk
CVE-2025-20322Same product: Splunk Splunk
CVE-2025-20300Same product: Splunk Splunk
CVE-2026-20259Same product: Splunk Splunk
CVE-2024-45737Same product: Splunk Splunk
CVE-2025-20320Same product: Splunk Splunk
CVE-2026-20202Same product: Splunk Splunk
CVE-2023-22931Same product: Splunk Splunk

Affected Assets

splunk
splunk
10.0.0 · 9.2.0 — 9.2.10 · 9.3.0 — 9.3.8 · 9.4.0 — 9.4.6
splunk
splunk cloud platform
9.3.2411 — 9.3.2411.117 · 10.0.2503 — 10.0.2503.6 · 10.1.2507 — 10.1.2507.4

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation can discover missing or incorrect output neutralization when log messages are constructed from untrusted input.

SI-10 Information Input Validation partial match

Input validation reduces the chance that specially crafted data reaches log-message construction routines.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices and coding standards directly require output sanitization for logs.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect log injection flaws but does not prevent them at the source.

A.8.15 Logging partial match
degrades

Logging control directly requires proper log generation and handling, which mitigates improper output neutralization.

A.8.16 Monitoring activities partial match
finds

Monitoring activities rely on trustworthy logs but do not ensure log message integrity.

A.8.25 Secure development life cycle partial match
prevents

Secure SDLC includes coding standards that reduce log-related weaknesses but does not specifically address logging.

A.8.28 Secure coding partial match
prevents

Secure coding practices mandate input validation and output encoding, directly preventing log injection.

References