Vulnerability Description
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.
CVSS Score
MEDIUM
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Apache | Pulsar | < 2.7.5 |
Related Weaknesses (CWE)
References
- https://lists.apache.org/thread/42v5rsxj36r3nhfxhmhb2x12r5jmvx3xMailing ListVendor Advisory
- https://lists.apache.org/thread/42v5rsxj36r3nhfxhmhb2x12r5jmvx3xMailing ListVendor Advisory
FAQ
What is CVE-2022-33683?
CVE-2022-33683 is a vulnerability with a CVSS score of 5.9 (MEDIUM). 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 Admi...
How severe is CVE-2022-33683?
CVE-2022-33683 has been rated MEDIUM with a CVSS base score of 5.9/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2022-33683?
Check the references section above for vendor advisories and patch information. Affected products include: Apache Pulsar.