Credential disclosure via missing TLS hostname verification
Published Sep 23, 2022 · Updated May 27, 2025
Improper certificate validation in Apache Pulsar allows man-in-the-middle attackers to read credentials and message data over TLS. In versions 2.6.4 and earlier, 2.7.0 through 2.7.4, 2.8.0 through 2.8.3, 2.9.0 through 2.9.2, and 2.10.0, internal Broker and Proxy clients do not enforce hostname matching for pulsar+ssl and HTTPS connections. An attacker must control a network path and present a valid certificate for an unrelated host, exposing credentials, configuration, messages, and other client data.
Summary
What happened
Improper certificate validation in Apache Pulsar allows man-in-the-middle attackers to read credentials and message data over TLS. In versions 2.6.4 and earlier, 2.7.0 through 2.7.4, 2.8.0 through 2.8.3, 2.9.0 through 2.9.2, and 2.10.0, internal Broker and Proxy clients do not enforce hostname matching for pulsar+ssl and HTTPS connections. An attacker must control a network path and present a valid certificate for an unrelated host, exposing credentials, configuration, messages, and other client data.
The record
- CVE
- CVE-2022-33682
- Published
- Sep 23, 2022
- Updated
- May 27, 2025
- Vendor
- The Apache Software Foundation
- Product
- Apache Pulsar
- Classifications
- CWE-295, T1557
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 23, 2022CVE publishedPublication date reported by the CVE source.
- May 27, 2025Record 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.
- Affected versionversion=2.10.0
- Affected versionversion=2.6 and earlier <=2.6.4
- Affected versionversion=2.7 <=2.7.4
- Affected versionversion=2.8 <=2.8.3
- Affected versionversion=2.9 <=2.9.2
What conditions does exploitation require?
What is affected?
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.
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