First published: Mon Jul 01 2024(Updated: )
In Splunk Enterprise versions below 9.2.2, 9.1.5, and 9.0.10 and Splunk Cloud Platform versions below 9.1.2312.109, an attacker could determine whether or not another user exists on the instance by deciphering the error response that they would likely receive from the instance when they attempt to log in. This disclosure could then lead to additional brute-force password-guessing attacks. This vulnerability would require that the Splunk platform instance uses the Security Assertion Markup Language (SAML) authentication scheme.
Credit: prodsec@splunk.com
Affected Software | Affected Version | How to fix |
---|---|---|
Splunk | >=9.0.0<=9.0.10 | |
Splunk | >=9.1.0<9.1.5 | |
Splunk | >=9.2.0<9.2.2 | |
Splunk Cloud Platform | >=9.1.2312<9.1.2312.109 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-36996 is classified as a high severity vulnerability due to its potential exploitation by attackers to infer user existence.
To remediate CVE-2024-36996, upgrade to Splunk Enterprise version 9.2.2 or higher, 9.1.5 or higher, or 9.0.10 or higher, or to Splunk Cloud Platform version 9.1.2312.109 or higher.
CVE-2024-36996 affects Splunk Enterprise versions below 9.2.2, 9.1.5, and 9.0.10, as well as Splunk Cloud Platform versions below 9.1.2312.109.
CVE-2024-36996 enables a user enumeration attack by allowing an attacker to determine if a user exists on the instance through error messages.
There is no documented workaround for CVE-2024-36996, so immediate upgrading is necessary for mitigation.