CVE-2022-33682

Disabled Hostname Verification makes Brokers, Proxies vulnerable to MITM attack

State
Published
Severity
5.9 Medium
Published
Sep 23, 2022
Updated
May 27, 2025
Reserved
Jun 15, 2022

Read the record on cve.org

Description

TLS hostname verification cannot be enabled in the Pulsar Broker's Java Client, the Pulsar Broker's Java Admin Client, the Pulsar WebSocket Proxy's Java Client, and the Pulsar Proxy's Admin Client leaving intra-cluster connections and geo-replication connections vulnerable to man in the middle attacks, which could leak credentials, configuration data, message data, and any other data sent by these clients. The vulnerability is for both the pulsar+ssl protocol and HTTPS. An attacker can only take advantage of this vulnerability by taking control of a machine 'between' the client and the server. The attacker must then actively manipulate traffic to perform the attack by providing the client with a cryptographically valid certificate for an unrelated host. This issue affects Apache Pulsar Broker, Proxy, and WebSocket Proxy versions 2.7.0 to 2.7.4; 2.8.0 to 2.8.3; 2.9.0 to 2.9.2; 2.10.0; 2.6.4 and earlier.

Scores

CVSSScoreVectorSource
3.15.9 MediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:NCISA-ADP

Weaknesses

  • CWE-295 Improper Certificate Validation

Affected Products

ProductVersions
Apache PulsarApache Software Foundation
  • 2.10.0Affected
  • 2.7 through 2.7.4Affected
  • 2.8 through 2.8.3Affected
  • 2.9 through 2.9.2Affected
  • 2.6 and earlier through 2.6.4Affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.