VYPR
Medium severity5.9NVD Advisory· Published Sep 23, 2022· Updated Jun 17, 2026

CVE-2022-33682

CVE-2022-33682

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.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

Affected packages

Versions sourced from the GitHub Security Advisory.

PackageAffected versionsPatched versions
org.apache.pulsar:pulsar-brokerMaven
< 2.7.52.7.5
org.apache.pulsar:pulsar-proxyMaven
< 2.7.52.7.5
org.apache.pulsar:pulsar-brokerMaven
>= 2.8.0, < 2.8.42.8.4
org.apache.pulsar:pulsar-proxyMaven
>= 2.8.0, < 2.8.42.8.4
org.apache.pulsar:pulsar-brokerMaven
>= 2.9.0, < 2.9.32.9.3
org.apache.pulsar:pulsar-proxyMaven
>= 2.9.0, < 2.9.32.9.3
org.apache.pulsar:pulsar-brokerMaven
>= 2.10.0, < 2.10.12.10.1
org.apache.pulsar:pulsar-proxyMaven
>= 2.10.0, < 2.10.12.10.1

Affected products

3

Patches

Vulnerability mechanics

References

3

News mentions

0

No linked articles in our index yet.