CVE-2022-33683
Description
Apache Pulsar Brokers and Proxies create an internal Pulsar Admin Client that does not verify peer TLS certificates, even when tlsAllowInsecureConnection is disabled via configuration. The Pulsar Admin Client's intra-cluster and geo-replication HTTPS connections are vulnerable to man in the middle attacks, which could leak authentication data, configuration data, and any other data sent by these clients. 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. This issue affects Apache Pulsar Broker and 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.
How to fix
- apache pulsar2.7.5, 2.8.4, 2.9.3 or later
- org.apache.pulsar:pulsar-broker2.7.5, 2.8.4, 2.9.3, 2.10.1 or later
- org.apache.pulsar:pulsar-proxy2.7.5, 2.8.4, 2.9.3, 2.10.1 or later
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| apache pulsar | v < 2.7.5, 2.8.0 ≤ v < 2.8.4, 2.9.0 ≤ v < 2.9.3, 2.10.0 | 2.7.5, 2.8.4, 2.9.3 |
| org.apache.pulsar:pulsar-brokerMaven | v < 2.7.5, 2.8.0 ≤ v < 2.8.4, 2.9.0 ≤ v < 2.9.3, 2.10.0 ≤ v < 2.10.1 | 2.7.5, 2.8.4, 2.9.3, 2.10.1 |
| org.apache.pulsar:pulsar-proxyMaven | v < 2.7.5, 2.8.0 ≤ v < 2.8.4, 2.9.0 ≤ v < 2.9.3, 2.10.0 ≤ v < 2.10.1 | 2.7.5, 2.8.4, 2.9.3, 2.10.1 |
Check your version
Choose the product and enter the version you run to see whether it falls in the affected range.
Attack Surface Management
See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.