GHSA-jvf3-mfxv-jcqr Apache Pulsar Broker, Proxy, and WebSocket Proxy 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

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.