Improper Hostname Verification in Java Client and Proxy can expose authentication data via MITM
Apache Software Foundation Apache Pulsar
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.apache.pulsar:pulsar-client Maven |
|
|
Apache Software Foundation Apache Pulsar
| Product | Affected | Fixed in |
|---|---|---|
| org.apache.pulsar:pulsar-client Maven |
|
|
Delayed TLS hostname verification in the Pulsar Java Client and the Pulsar Proxy make each client vulnerable to a man in the middle attack. Connections from the Pulsar Java Client to the Pulsar Broker/Proxy and connections from the Pulsar Proxy to the Pulsar Broker are vulnerable. Authentication data is sent before verifying the server’s TLS certificate matches the hostname, which means authentication data could be exposed to an attacker. 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. Because the client sends authentication data before performing hostname verification, an attacker could gain access to the client’s authentication data. The client eventually closes the connection when it verifies the hostname and identifies the targeted hostname does not match a hostname on the certificate. Because the client eventually closes the connection, the value of the intercepted authentication data depends on the authentication method used by the client. Token based authentication and username/password authentication methods are vulnerable because the authentication data can be used to impersonate the client in a separate session. This issue affects Apache Pulsar Java Client 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.
From the CVE record · apache
The Pulsar Java Client and Pulsar Proxy send authentication data before verifying that the server’s TLS certificate matches its hostname. An attacker who controls a machine between the client and server can actively manipulate traffic and present a valid certificate for an unrelated host, potentially capturing authentication data. Token and username/password authentication data can be used to impersonate the client in a separate session.
Teams running the Apache Pulsar Java Client in versions 2.6.4 and earlier, 2.7.0–2.7.4, 2.8.0–2.8.3, 2.9.0–2.9.2, or 2.10.0, or running the Pulsar Proxy, should check their exposure.