org.apache.pulsar:pulsar-proxy@2.0.1-incubating vulnerabilities
latest version
4.0.1
latest non vulnerable version
first published
7 years ago
latest version published
17 days ago
licenses detected
- [1.19.0-incubating,)
package manager
Direct Vulnerabilities
Known vulnerabilities in the org.apache.pulsar:pulsar-proxy package. This does not include vulnerabilities belonging to this package’s dependencies.
How to fix?
Automatically find and fix vulnerabilities affecting your projects. Snyk scans for vulnerabilities and provides fixes for free.
Fix for free| Vulnerability | Vulnerable Version |
|---|---|
Affected versions of this package are vulnerable to Improper Certificate Validation due to Apache Pulsar Brokers and Proxies creating an internal Pulsar Admin Client that does not verify peer TLS certificates, even when How to fix Improper Certificate Validation? Upgrade | [,2.7.5)[2.8.0,2.8.4)[2.9.0,2.9.3)[2.10.0,2.10.1) |
Affected versions of this package are vulnerable to Man-in-the-Middle (MitM) due to the TLS hostname verification which 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. How to fix Man-in-the-Middle (MitM)? Upgrade | [,2.7.5)[2.8.0,2.8.4)[2.9.0,2.9.3)[2.10.0,2.10.1) |
Affected versions of this package are vulnerable to Improper Certificate Validation when the authentication data is sent before verifying if 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. How to fix Improper Certificate Validation? Upgrade | [,2.7.5)[2.8.0,2.8.4)[2.9.0,2.9.3)[2.10.0,2.10.1) |
Affected versions of this package are vulnerable to Improper Input Validation by allowing an attacker to send TCP/IP connection attempts that originate from the Pulsar Proxy's IP address. When the Apache Pulsar Proxy component is used, it is possible to attempt to open TCP/IP connections to any IP address and port that the Pulsar Proxy can connect to. An attacker could use this as a way for DoS attacks that originate from the Pulsar Proxy's IP address. It hasn’t been detected that the Pulsar Proxy authentication can be bypassed. The attacker will have to have a valid token to a properly secured Pulsar Proxy. How to fix Improper Input Validation? Upgrade | [,2.7.5)[2.8.0,2.8.3)[2.9.0,2.9.2) |