First published: Fri Sep 23 2022(Updated: )
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.
Credit: security@apache.org
Affected Software | Affected Version | How to fix |
---|---|---|
Apache Pulsar | <2.7.5 | |
Apache Pulsar | >=2.8.0<2.8.4 | |
Apache Pulsar | >=2.9.0<2.9.3 | |
Apache Pulsar | =2.10.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2022-33683 is a vulnerability in Apache Pulsar Brokers and Proxies that allows man-in-the-middle attacks on intra-cluster and geo-replication HTTPS connections.
CVE-2022-33683 has a severity score of 5.9, which is considered medium.
CVE-2022-33683 affects Apache Pulsar versions up to and including 2.7.5, versions between 2.8.0 and 2.8.4, versions between 2.9.0 and 2.9.3, and version 2.10.0.
To fix CVE-2022-33683, upgrade to a version of Apache Pulsar that is not affected by the vulnerability.
More information about CVE-2022-33683 can be found at the following reference link: [https://lists.apache.org/thread/42v5rsxj36r3nhfxhmhb2x12r5jmvx3x](https://lists.apache.org/thread/42v5rsxj36r3nhfxhmhb2x12r5jmvx3x)