~ / search / GHSA-j3qw-g67q-7m64

GHSA-j3qw-g67q-7m64

Apache Pulsar Brokers and Proxies vulnerable to Improper Certificate Validation

Source: GitHub Advisory Database (reviewed) Moderate CVE-2022-33683

Packages

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

Details

As written in the advisory (Markdown source, shown as plain text).

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.

References

External links from the advisory. They lead to third-party sites.