Disabled Certificate Validation makes Broker, Proxy Admin Clients vulnerable to MITM attack
Apache Software Foundation Apache Pulsar
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.apache.pulsar:pulsar-broker Maven |
|
|
Apache Software Foundation Apache Pulsar
| Product | Affected | Fixed in |
|---|---|---|
| org.apache.pulsar:pulsar-broker Maven |
|
|
| org.apache.pulsar:pulsar-proxy Maven |
|
|
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.
From the CVE record · apache
Apache Pulsar brokers and proxies create an internal Admin Client that does not verify peer TLS certificates, even when insecure connections are disabled. An attacker who controls a machine between the client and server and actively manipulates HTTPS traffic could expose authentication, configuration, or other data sent by the client.
Operators running Apache Pulsar brokers or proxies in versions 2.6.4 and earlier, 2.7.0–2.7.4, 2.8.0–2.8.3, 2.9.0–2.9.2, or 2.10.0 should check their deployments.