CVE-2022-32153Network attack vector

Peer traffic interception via missing hostname validation

Published Jun 15, 2022 · Updated Sep 16, 2024

Improper TLS host name validation in Splunk Enterprise and Splunk Cloud Platform allows man-in-the-middle attackers to intercept peer traffic. Affected releases accept a peer certificate without matching its CN or SAN to the requested host name, allowing an impostor with an otherwise trusted certificate to complete the TLS connection. Exploitation requires a nondefault customer CA chain, compromise of a valid certificate in that chain, and a network position between peers; default certificates are not vulnerable.

CVSS severity8.1
High
EPSS probability0.90%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Improper TLS host name validation in Splunk Enterprise and Splunk Cloud Platform allows man-in-the-middle attackers to intercept peer traffic. Affected releases accept a peer certificate without matching its CN or SAN to the requested host name, allowing an impostor with an otherwise trusted certificate to complete the TLS connection. Exploitation requires a nondefault customer CA chain, compromise of a valid certificate in that chain, and a network position between peers; default certificates are not vulnerable.

The record

CVE
CVE-2022-32153
Published
Jun 15, 2022
Updated
Sep 16, 2024
Vendor
Splunk, Inc.
Product
Splunk Enterprise
Classifications
CWE-297, CWE-295, T1557
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Jun 15, 2022CVE publishedPublication date reported by the CVE source.
  2. Sep 16, 2024Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=9.0 <9.0

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Splunk, Inc. · Splunk Enterpriseversion=9.0 <9.0
Splunk, Inc. · Splunk Cloud Platformversion=8.2 <8.2.2203

Published CVSS scores

8.1Splunk Inc.CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
6.8NIST NVDAV:N/AC:M/Au:N/C:P/I:P/A:P

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-297Improper Validation of Certificate with Host Mismatch
CWE-295Improper Certificate Validation
T1557Adversary-in-the-Middle

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo