Plaintext password disclosure via DEBUG logging
Published Oct 14, 2024 · Updated Feb 28, 2025
Information disclosure in Splunk Enterprise 9.1.0 through 9.1.5, 9.2.0 through 9.2.2, and 9.3.0 allows attackers to read plaintext passwords. When AdminManager is set to DEBUG, splunkd writes local native-authentication passwords in plaintext to logs that feed the internal index. Exposure requires the DEBUG setting plus local log-file access or administrative access to internal indexes.
Summary
What happened
Information disclosure in Splunk Enterprise 9.1.0 through 9.1.5, 9.2.0 through 9.2.2, and 9.3.0 allows attackers to read plaintext passwords. When AdminManager is set to DEBUG, splunkd writes local native-authentication passwords in plaintext to logs that feed the internal index. Exposure requires the DEBUG setting plus local log-file access or administrative access to internal indexes.
The record
- CVE
- CVE-2024-45739
- Published
- Oct 14, 2024
- Updated
- Feb 28, 2025
- Vendor
- Splunk, Inc.
- Product
- Splunk Enterprise
- Classifications
- CWE-532, CWE-200
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Oct 14, 2024CVE publishedPublication date reported by the CVE source.
- Feb 28, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=9.1 <9.1.6
- Affected versionversion=9.2 <9.2.3
- Affected versionversion=9.3 <9.3.1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo