dbcve.org
SplunkApplication

CVE-2022-43562

MEDIUM · 5.4 CVSS v3.1 Published 2022-11-04
Fix available
A fix is available. Upgrade to 8.1.12 / 8.2.9 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In Splunk Enterprise versions below 8.1.12, 8.2.9, and 9.0.2, Splunk Enterprise fails to properly validate and escape the Host header, which could let a remote authenticated user conduct various attacks against the system, including cross-site scripting and cache poisoning.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Splunk Enterprise fails to properly validate and escape the Host HTTP header, allowing authenticated remote users to inject malicious content through the header. This improper input handling enables cross-site scripting (XSS) attacks and cache poisoning attacks against the application.

MitigationUpgrade Splunk Enterprise to version 8.1.12, 8.2.9, 9.0.2 or later to obtain the patched version that properly validates and escapes the Host header.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
SplunkApplication
Affected:>= 8.1.0, < 8.1.12>= 8.2.0, < 8.2.9>= 9.0.0, < 9.0.2
Splunk Cloud PlatformApplication
Affected:< 9.0.2208

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify your Splunk product and version
    Run command: $SPLUNK_HOME/bin/splunk version OR check via Splunk web UI under Settings > About > Version
    Affected if The version falls within any of these vulnerable ranges: Enterprise 8.1.0-8.1.11, 8.2.0-8.2.8, or 9.0.0-9.0.1; or Cloud Platform versions below 9.0.2208
  2. Confirm Splunk Enterprise version is vulnerable
    Compare your installed Enterprise version number to the affected ranges: 8.1.x where x < 12, 8.2.x where x < 9, or 9.0.x where x < 2
    Affected if Your Enterprise version is 8.1.0 through 8.1.11, 8.2.0 through 8.2.8, or 9.0.0 through 9.0.1
  3. Confirm Splunk Cloud Platform version is vulnerable
    Check your Cloud Platform version in the Splunk Cloud management console or contact Splunk support for version details
    Affected if Your Cloud Platform version is earlier than 9.0.2208

You are affected if you are running any Splunk Enterprise version 8.1.0-8.1.11, 8.2.0-8.2.8, 9.0.0-9.0.1, or Splunk Cloud Platform below 9.0.2208.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 8.1.12 / 8.2.9 / 9.0.2 or later
Fixed in 8.1.128.2.99.0.2
Interim mitigation

Upgrade Splunk Enterprise to version 8.1.12, 8.2.9, 9.0.2 or later to obtain the patched version that properly validates and escapes the Host header.

Recommended fix High confidence

Splunk Enterprise: 8.1.12, 8.2.9, or 9.0.2 (choose based on current version branch); Splunk Cloud Platform: 9.0.2208 or later

  1. 1. Identify current Splunk Enterprise version by navigating to Settings > About or running 'splunk version' from CLI
  2. 2. Determine target upgrade version based on current branch: if 8.1.x upgrade to 8.1.12; if 8.2.x upgrade to 8.2.9; if 9.0.x upgrade to 9.0.2
  3. 3. Review Splunk upgrade documentation for your version path at docs.splunk.com
  4. 4. Create a full backup of Splunk configuration files, apps, and indexes before upgrading
  5. 5. Stop Splunk services before performing upgrade
  6. 6. Download the appropriate Splunk Enterprise upgrade package from splunk.com/products/splunk
  7. 7. Install the upgrade following standard Splunk upgrade procedures
  8. 8. Start Splunk services and verify successful startup
Caveat Review Splunk Enterprise upgrade notes for potential impacts to custom apps, configs, or index structures when moving between minor versions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Splunk Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,780
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,448.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-43562 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-43562 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data