Security readout for executives and security teams
Plain-English summary
CVE-2022-43562 is a low-severity Splunk Enterprise issue where trusted request headers are not handled safely. An authenticated, highly privileged remote user could abuse the Host header to support attacks such as cross-site scripting or cache poisoning. It is not listed in KEV, so public evidence here does not support active exploitation.
Executive priority
Handle through normal vulnerability management unless the affected Splunk instance is highly exposed or administered by many privileged users. The business risk is real but constrained by authentication, high privilege requirements, high attack complexity, and low CVSS severity.
Technical view
Splunk Enterprise versions below 8.1.12, 8.2.9, and 9.0.2 fail to properly validate and escape the Host header. The CVSS 3.1 vector is AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:N/A:N, indicating network reachability, high complexity, high privileges required, changed scope, and limited confidentiality impact.
Likely exposure
Exposure applies to Splunk Enterprise 8.1, 8.2, and 9.0 deployments below the fixed versions. Risk is most relevant where authenticated high-privilege users can reach the affected Splunk Enterprise service and where Host-header-derived content could influence browser or cache behavior.
Exploitation context
The provided sources describe possible cross-site scripting and cache poisoning outcomes, but do not provide evidence of active exploitation. The vulnerability requires authentication and high privileges per CVSS, and attack complexity is high, which lowers practical urgency compared with unauthenticated Splunk flaws.
Researcher notes
The source bundle identifies CWE-20 and Host header validation and escaping failure. It does not include exploit details, compensating controls, or confirmed exploitation. Validation should focus on accurate version detection, privileged access paths, and whether affected Splunk Enterprise instances remain deployed.
Mitigation direction
- Upgrade Splunk Enterprise to 8.1.12, 8.2.9, 9.0.2, or later supported releases.
- Review Splunk advisory SVD-2022-1102 for vendor-specific remediation guidance.
- Prioritize internet-accessible or broadly administered Splunk Enterprise instances first.
- Limit Splunk Enterprise access to trusted administrators while upgrades are pending.
- Monitor vendor advisories for any revised exploitation or mitigation guidance.
Validation and detection
- Inventory Splunk Enterprise versions across production, staging, and administrative environments.
- Confirm no instance remains below 8.1.12, 8.2.9, or 9.0.2.
- Review access controls for users with high privileges on Splunk Enterprise.
- Check security monitoring for suspicious authenticated web activity involving affected Splunk systems.
- Document remediation status against the Splunk advisory and CVE record.
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-20: 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 lookupCVE-2022-43562 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
- Low
- CVSS
- 3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/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:H/PR:H/UI:N/S:C/C:L/I:N/A:N1.31.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
3LowVector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/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-1102.htmlCVE reference
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.
Improper Input Validation
Improper Input Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.