Daemon crash via recursive XML entity expansion
Published Jun 1, 2023 · Updated Feb 28, 2025
XML entity expansion in Splunk Enterprise before 8.1.14, 8.2.11, or 9.0.5 allows remote attackers to crash splunkd through SAML SSO. The SAML authentication XML parser expands recursive entity references until available memory is exhausted, after which splunkd crashes or is terminated. Splunk Cloud Platform before 9.0.2303.100 is also affected; SAML SSO must be enabled, and the reported consequence is service interruption without data disclosure or modification.
Summary
What happened
XML entity expansion in Splunk Enterprise before 8.1.14, 8.2.11, or 9.0.5 allows remote attackers to crash splunkd through SAML SSO. The SAML authentication XML parser expands recursive entity references until available memory is exhausted, after which splunkd crashes or is terminated. Splunk Cloud Platform before 9.0.2303.100 is also affected; SAML SSO must be enabled, and the reported consequence is service interruption without data disclosure or modification.
The record
- CVE
- CVE-2023-32706
- Published
- Jun 1, 2023
- Updated
- Feb 28, 2025
- Vendor
- Splunk, Inc.
- Product
- Splunk Enterprise
- Classifications
- CWE-611, T1499.004
- Attack vector
- network
- Privileges
- Unavailable
Timeline
How it unfolded
- Jun 1, 2023CVE 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=8.1 <8.1.14
- Affected versionversion=8.2 <8.2.11
- Affected versionversion=9.0 <9.0.5
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