Vulnerability in Apache Pulsar
CVE-2022-33682
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.
Vulnerability class: Improper Certificate Validation
Published · last modified .
CVSS v3 metric
CVSS v3 base score 5.9 (Medium). Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N.
EPSS exploit prediction
EPSS 0.007, 54.4th percentile (scored ); unchanged over 30 days. About EPSS.
Affected products
- Apache Pulsar — versions 2.10.0
- Apache Software Foundation Pulsar — versions 2.10.0, 2.7, 2.8
Weakness classification (CWE)
Public exploits and proof-of-concept code
Also mentioned in 1 other repository (karimhabush/cyberowl). These reference the CVE in a list, notes or a scanner and are not exploit code for it.
References
- lists.apache.org/thread/l0ynfl161qghwfcgbbl8ld9hzbl9t3yx (Mailing List, Vendor Advisory)