CVE-2024-36996 json
Information Disclosure of user names
published 2y ago modified 4mo ago also EUVD-2024-36383
- cvss
- 5.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 29%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Splunk Splunk Enterprise 9.0.10, 9.1.5, 9.2.2
- Splunk Splunk Cloud Platform 9.1.2312.109
- splunk splunk_enterprise 9.0.10, 9.1.5, 9.2.2
- splunk splunk_cloud_platform 9.1.2312.109
Is CVE-2024-36996 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 2y ago
Exploit prediction
0.35% chance of exploitation in the next 30 days, higher than 29% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
| NVD | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
Affected products
- Splunk Splunk Enterprise
- Splunk Splunk Cloud Platform
- splunk splunk_enterprise
- splunk splunk_cloud_platform
Classification
References
-
advisory.splunk.com
/advisories/SVD-2024-0716
vendor-advisory
Sources
- CVE List CVE-2024-36996
- NVD CVE-2024-36996
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.