Cyber Resilience

CVE-2024-36996

Splunk 9.0.0 – 9.0.10

Published
01 July 2024
Modified
21 November 2024
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:L/I:N/A:N
EPSS Score 0.0035 28th percentile
Risk Priority 45 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2024-36996 is a medium-severity Observable Response Discrepancy (CWE-204) vulnerability in Splunk Splunk. Its CVSS base score is 5.3 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Account Discovery (T1087); ranked at the 28th 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 IA-6 (Authentication Feedback) and SI-11 (Error Handling) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

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…

more

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.

CWE(s)
CWE-204CWE-203

Related Threats

MITRE ATT&CK Enterprise Techniques

T1087 Account Discovery Discovery
Adversaries may attempt to get a listing of valid accounts, usernames, or email addresses on a system or within a compromised environment.
attack.mitre.org →
T1087.001 Local Account Discovery
Adversaries may attempt to get a listing of local system accounts.
attack.mitre.org →
T1087.002 Domain Account Discovery
Adversaries may attempt to get a listing of domain accounts.
attack.mitre.org →
T1087.003 Email Account Discovery
Adversaries may attempt to get a listing of email addresses and accounts.
attack.mitre.org →
T1087.004 Cloud Account Discovery
Adversaries may attempt to get a listing of cloud accounts.
attack.mitre.org →
T1110 Brute Force Credential Access
Adversaries may use brute force techniques to gain access to accounts when passwords are unknown or when password hashes are obtained.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-20298Same product: Splunk Splunk
CVE-2025-20226Same product: Splunk Splunk
CVE-2024-53244Same product: Splunk Splunk
CVE-2026-20166Same product: Splunk Splunk
CVE-2025-20232Same product: Splunk Splunk
CVE-2026-20164Same product: Splunk Splunk
CVE-2025-20325Same product: Splunk Splunk
CVE-2024-53245Same product: Splunk Splunk
CVE-2025-20379Same product: Splunk Splunk
CVE-2023-32710Same product: Splunk Splunk

Affected Assets

splunk
splunk
9.0.0 — 9.0.10 · 9.1.0 — 9.1.5 · 9.2.0 — 9.2.2
splunk
splunk cloud platform
9.1.2312 — 9.1.2312.109

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)
  • 1 hardening rule · 1 OS baseline
Validate
Prove the fix (OWASP ASVS)
  • V13.4.5

Mitigating Controls (NIST 800-53 r5) AI

IA-6 Authentication Feedback good match

Obscuring authentication feedback directly stops one common source of observable response discrepancies.

SI-11 Error Handling good match

Error handling explicitly requires messages that avoid revealing exploitable internal information.

AC-4 Information Flow Enforcement partial match

Information flow enforcement can block responses that would otherwise disclose internal state to unauthorized parties.

SC-7 Boundary Protection partial match

Boundary protection monitors and filters outbound responses that could leak internal state.

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 full match
prevents

Secure SDLC practices directly prevent introduction of inconsistent response behavior that leaks internal state.

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 observable response discrepancies before deployment.

A.8.20 Networks security partial match
mitigates

Network security controls can enforce uniform responses and suppress observable discrepancies.

A.8.25 Secure development life cycle partial match
prevents

Secure SDLC practices include error-handling and response standardization to avoid information disclosure.

A.8.26 Application security requirements partial match
prevents

Application security requirements typically mandate consistent, non-revealing error messages.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles discourage designs that leak internal state via differing responses.

A.8.28 Secure coding partial match
prevents

Secure coding standards explicitly require uniform error handling to prevent information leakage.

References