Security readout for executives and security teams
Plain-English summary
This issue lets an unauthenticated person tell whether a username exists in certain Splunk Enterprise deployments by observing a lockout-related REST API message. It does not grant access by itself, but it can help attackers refine phishing, password spraying, or credential attacks against known accounts.
Executive priority
Treat as a moderate-priority hardening item. It is not remote code execution, but it can reduce attacker guesswork against a security-critical platform and support follow-on credential attacks.
Technical view
CVE-2021-33845 is a CWE-203 information-disclosure flaw in Splunk Enterprise before 8.1.7. When verbose login errors are repressed, the REST API lockout error behavior can still reveal valid usernames. CVSS is 5.3: network reachable, low complexity, no privileges, no user interaction, confidentiality impact only.
Likely exposure
Exposure is limited to Splunk Enterprise instances before 8.1.7 configured to repress verbose login errors. Publicly reachable REST API surfaces increase practical risk. Current-source evidence does not identify other Splunk products or versions as affected.
Exploitation context
The source bundle does not show CISA KEV listing or confirmed active exploitation. Splunk publishes detection content for user enumeration attempts, which supports monitoring for suspicious probing, but that is not evidence of active exploitation.
Researcher notes
Key constraints are the specific affected version range and configuration dependency. Do not generalize beyond Splunk Enterprise before 8.1.7. Detection should focus on repeated username probing patterns without attempting to reproduce offensive enumeration behavior.
Mitigation direction
- Upgrade affected Splunk Enterprise instances to 8.1.7 or later.
- Review Splunk advisory SVD-2022-0502 for vendor remediation guidance.
- Inventory Splunk Enterprise versions and verbose login error settings.
- Prioritize internet-accessible or externally integrated Splunk management surfaces.
- Monitor for username enumeration attempts using Splunk’s published detection content.
Validation and detection
- Confirm whether any Splunk Enterprise instance is below 8.1.7.
- Check whether verbose login errors are configured to be repressed.
- Verify remediation by confirming the running Splunk Enterprise fixed version.
- Review authentication and REST API logs for enumeration-like patterns.
- Use Splunk’s detection reference to guide non-invasive monitoring.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-203: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2021-33845 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N3.91.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.splunk.com/en_us/product-security/announcements/svd-2022-0502.htmlCVE reference · x_refsource_MISC
- https://research.splunk.com/application/splunk_user_enumeration_attempt/CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Observable Discrepancy
Observable Discrepancy represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.