Security readout for executives and security teams
Plain-English summary
This flaw lets an unauthenticated sender bypass Splunk S2S TCP Token checks and write arbitrary events into an affected indexer. For executives, the business risk is log integrity: attackers could pollute indexed data, undermine investigations, and affect alerting decisions where vulnerable TCPTokens-enabled indexers are reachable.
Executive priority
Treat as a high-priority remediation for Splunk environments using TCPTokens. The issue affects trust in security telemetry rather than direct data theft, which can still materially impair detection, response, compliance reporting, and incident reconstruction.
Technical view
CVE-2021-31559 is a CWE-288 authentication bypass in Splunk Enterprise Indexer. A crafted request can bypass S2S TcpToken authentication and write arbitrary events to an index. Affected versions are Splunk Enterprise 8.1 before 8.1.5 and 8.2 before 8.2.1 when Indexers use TCPTokens. Universal Forwarders are not affected.
Likely exposure
Exposure is limited to Splunk Enterprise Indexers on affected versions configured to use TCPTokens. Risk increases if indexer receiving paths are reachable from untrusted networks, partners, compromised forwarder hosts, or poorly segmented internal systems.
Exploitation context
The provided sources do not state active exploitation, and the bundle marks CISA KEV as false. The CVSS vector is network-reachable, low complexity, no privileges, no user interaction, with high integrity impact and no stated confidentiality or availability impact.
Researcher notes
Testing should focus on configuration and exposure confirmation, not offensive reproduction. The key conditions are affected Splunk Enterprise Indexer version, TCPTokens enabled, and reachable S2S ingestion path. Sources do not provide exploit prevalence or detailed compensating controls beyond fixed versions.
Mitigation direction
- Upgrade Splunk Enterprise 8.1 deployments to 8.1.5 or later.
- Upgrade Splunk Enterprise 8.2 deployments to 8.2.1 or later.
- Identify Indexers configured to use TCPTokens.
- Restrict network access to indexer receiving interfaces to trusted sources.
- Review Splunk vendor guidance before applying compensating controls.
Validation and detection
- Inventory Splunk Enterprise Indexer versions and compare against fixed releases.
- Confirm whether each Indexer is configured to use TCPTokens.
- Verify Universal Forwarders are not treated as affected assets.
- Review indexer network exposure from untrusted or broad internal networks.
- Look for unexpected event sources or anomalous indexed data around vulnerable indexers.
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-288: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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 lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2021-31559 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
- High
- CVSS
- 7.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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:N/I:H/A:N3.93.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.splunk.com/en_us/product-security/announcements/svd-2022-0503.htmlCVE 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.
Authentication Bypass Using an Alternate Path or Channel
Authentication Bypass Using an Alternate Path or Channel represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.