GHSA-j3qw-g67q-7m64 Apache Pulsar Brokers and Proxies vulnerable to Improper Certificate Validation

• Maven org.apache.pulsar:pulsar-broker: < 2.7.5 → fixed in 2.7.5 • Maven org.apache.pulsar:pulsar-proxy: < 2.7.5 → fixed in 2.7.5 • Maven org.apache.pulsar:pulsar-broker: >= 2.8.0, < 2.8.4 → fixed in 2.8.4 • Maven org.apache.pulsar:pulsar-proxy: >= 2.8.0, < 2.8.4 → fixed in 2.8.4 • Maven org.apache.pulsar:pulsar-broker: >= 2.9.0, < 2.9.3 → fixed in 2.9.3 • Maven org.apache.pulsar:pulsar-proxy: >= 2.9.0, < 2.9.3 → fixed in 2.9.3 • Maven org.apache.pulsar:pulsar-broker: >= 2.10.0, < 2.10.1 → fixed in 2.10.1 • Maven org.apache.pulsar:pulsar-proxy: >= 2.10.0, < 2.10.1 → fixed in 2.10.1

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.