CVE-2022-43572
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 · uneditedIn Splunk Enterprise versions below 8.2.9, 8.1.12, and 9.0.2, sending a malformed file through the Splunk-to-Splunk (S2S) or HTTP Event Collector (HEC) protocols to an indexer results in a blockage or denial-of-service preventing further indexing.
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 confidenceThis is a denial-of-service vulnerability in Splunk Enterprise where sending malformed files through Splunk-to-Splunk (S2S) or HTTP Event Collector (HEC) protocols to an indexer causes the indexing process to block or fail, preventing any further data from being indexed.
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>= 8.1.0, < 8.1.12>= 8.2.0, < 8.2.9>= 9.0.0, < 9.0.2< 9.0.2209CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Check installed Splunk Enterprise versionRun the command: splunk --version or access the About page in Splunk Web (Settings > About) to view the exact version numberAffected if The version is 8.1.0 through 8.1.11, 8.2.0 through 8.2.8, or 9.0.0 through 9.0.1
-
Verify if Splunk-to-Splunk (S2S) receiving is configuredCheck for S2S receiver configuration in $SPLUNK_HOME/etc/system/default/outputs.conf or in Splunk Web under Settings > Forwarding and Receiving > Receive DataAffected if S2S receiving is enabled and the instance acts as a receiver for data from other Splunk instances
-
Verify if HTTP Event Collector (HEC) is enabledCheck Splunk Web under Settings > Data Inputs > HTTP Event Collector, or inspect $SPLUNK_HOME/etc/system/default/inputs.conf for [http] stanzasAffected if HEC is enabled and configured to receive data over HTTP/HTTPS
You are affected if your Splunk Enterprise version falls within the vulnerable ranges AND you have S2S receiving or HEC enabled, allowing external malformed data to reach your indexer.
Generated from the published advisory. Verify against your own configuration.
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 · scoped8.1.128.2.99.0.2
Upgrade Splunk Enterprise to version 8.2.9, 8.1.12, 9.0.2 or later to resolve the malformed file handling issue in the indexing pipeline.
Splunk Enterprise: 8.1.12, 8.2.9, or 9.0.2 (and respective later versions); Splunk Cloud Platform: 9.0.2209
- Back up your Splunk configuration and data directories before proceeding with the upgrade
- Upgrade Splunk Enterprise to version 8.1.12 or later if currently on 8.1.x
- Upgrade Splunk Enterprise to version 8.2.9 or later if currently on 8.2.x
- Upgrade Splunk Enterprise to version 9.0.2 or later if currently on 9.0.x
- For Splunk Cloud Platform, contact Splunk support to ensure the instance is updated to version 9.0.2209 or later
- After upgrade, verify that the Splunk services are running and the malformed file issue is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-43572 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-43572 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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