org.apache.pulsar:pulsar-broker 2.0.1-incubating vulnerabilities

Direct Vulnerabilities

Known vulnerabilities in the org.apache.pulsar:pulsar-broker 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
M Insufficient Session Expiration Affected versions of this package are vulnerable to Insufficient Session Expiration which allows a client to stay connected to a broker after authentication data expires if the client connected through the Pulsar Proxy when the broker is configured with `authenticateOriginalAuthData=false` or if a client connects directly to a broker with a specially crafted connect command when the broker is configured with `authenticateOriginalAuthData=false`. How to fix Insufficient Session Expiration? Upgrade `org.apache.pulsar:pulsar-broker` to version 2.9.5, 2.10.4, 2.11.1 or higher.	[,2.9.5)[2.10.0,2.10.4)[2.11.0,2.11.1)
H Access Restriction Bypass Affected versions of this package are vulnerable to Access Restriction Bypass. When a client connects to the Pulsar Function Worker via the Pulsar Proxy where the Pulsar Proxy uses mTLS authentication to authenticate with the Pulsar Function Worker, the Pulsar Function Worker incorrectly performs authorization by using the Proxy's role for authorization instead of the client's role, which can lead to privilege escalation, especially if the proxy is configured with a superuser role. How to fix Access Restriction Bypass? Upgrade `org.apache.pulsar:pulsar-broker` to version 2.9.0, 2.10.4, 2.11.1 or higher.	[,2.9.0)[2.10.0,2.10.4)[2.11.0,2.11.1)
M Improper Certificate Validation 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 `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. How to fix Improper Certificate Validation? Upgrade `org.apache.pulsar:pulsar-broker` to version 2.7.5, 2.8.4, 2.9.3, 2.10.1 or higher.	[,2.7.5)[2.8.0,2.8.4)[2.9.0,2.9.3)[2.10.0,2.10.1)
M Improper Authorization Affected versions of this package are vulnerable to Improper Authorization due to improper validation of Pulsar admin method `getMessageById`, which makes it possible for a user to read from a ledger that contains data owned by another tenant. How to fix Improper Authorization? Upgrade `org.apache.pulsar:pulsar-broker` to version 2.8.1 or higher.	[,2.8.1)

Vulnerability

Vulnerable Version

Insufficient Session Expiration

Affected versions of this package are vulnerable to Insufficient Session Expiration which allows a client to stay connected to a broker after authentication data expires if the client connected through the Pulsar Proxy when the broker is configured with authenticateOriginalAuthData=false or if a client connects directly to a broker with a specially crafted connect command when the broker is configured with authenticateOriginalAuthData=false.

How to fix Insufficient Session Expiration?

Upgrade org.apache.pulsar:pulsar-broker to version 2.9.5, 2.10.4, 2.11.1 or higher.

[,2.9.5)[2.10.0,2.10.4)[2.11.0,2.11.1)

Access Restriction Bypass

Affected versions of this package are vulnerable to Access Restriction Bypass. When a client connects to the Pulsar Function Worker via the Pulsar Proxy where the Pulsar Proxy uses mTLS authentication to authenticate with the Pulsar Function Worker, the Pulsar Function Worker incorrectly performs authorization by using the Proxy's role for authorization instead of the client's role, which can lead to privilege escalation, especially if the proxy is configured with a superuser role.

How to fix Access Restriction Bypass?

Upgrade org.apache.pulsar:pulsar-broker to version 2.9.0, 2.10.4, 2.11.1 or higher.

[,2.9.0)[2.10.0,2.10.4)[2.11.0,2.11.1)

Improper Certificate Validation

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 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.

How to fix Improper Certificate Validation?

Upgrade org.apache.pulsar:pulsar-broker to version 2.7.5, 2.8.4, 2.9.3, 2.10.1 or higher.

[,2.7.5)[2.8.0,2.8.4)[2.9.0,2.9.3)[2.10.0,2.10.1)

Improper Authorization

Affected versions of this package are vulnerable to Improper Authorization due to improper validation of Pulsar admin method getMessageById, which makes it possible for a user to read from a ledger that contains data owned by another tenant.

How to fix Improper Authorization?

Upgrade org.apache.pulsar:pulsar-broker to version 2.8.1 or higher.

[,2.8.1)

org.apache.pulsar:pulsar-broker@2.0.1-incubating vulnerabilities

latest version

latest non vulnerable version

first published

latest version published

licenses detected

package manager

Direct Vulnerabilities

How to fix?