org.apache.pulsar:pulsar-broker vulnerabilities
Apache Pulsar :: pulsar-broker
- Registry
- Maven
- Latest
- 5.0.1
6 known advisories
The latest version, 5.0.1, is not affected by any of them. Projects on older versions may be.
mvn versions:use-dep-version -Dincludes=org.apache.pulsar:pulsar-broker -DdepVersion=5.0.1 -DforceVersion=trueIs your project on an affected org.apache.pulsar:pulsar-broker?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Security advisories for org.apache.pulsar:pulsar-broker
Apache Pulsar: Improper Authorization For Namespace and Topic Management Endpoints
- Affected
- >=2.7.1 <=2.10.6 · >=2.11.0 <=2.11.4 · >=3.0.0 <3.0.4 · >=3.1.0 <=3.1.3 · >=3.2.0 <3.2.2
- Fixed in
- 3.0.4, 3.2.2
Apache Pulsar: Improper Authorization For Topic-Level Policy Management
- Affected
- >=3.2.0 <3.2.1 · >=3.1.0 <3.1.3 · >=3.0.0 <3.0.3 · >=2.11.0 <2.11.4 · >=2.7.1 <2.10.6
- Fixed in
- 2.10.6, 2.11.4, 3.0.3, 3.1.3, 3.2.1
Apache Pulsar Broker's Rest Producer vulnerable to Incorrect Authorization
- Affected
- >=2.9.0 <2.10.4 · >=2.11.0 <2.11.1
- Fixed in
- 2.10.4, 2.11.1
Apache Pulsar Broker Improper Authentication vulnerability
- Affected
- >=2.9.0 <2.10.4 · >=2.11.0 <2.11.1
- Fixed in
- 2.10.4, 2.11.1
Apache Pulsar Brokers and Proxies vulnerable to Improper Certificate Validation
- Affected
- <2.7.5 · >=2.8.0 <2.8.4 · >=2.9.0 <2.9.3 · >=2.10.0 <2.10.1
- Fixed in
- 2.7.5, 2.8.4, 2.9.3, 2.10.1
Apache Pulsar Broker, Proxy, and WebSocket Proxy vulnerable to Improper Certificate Validation
- Affected
- <2.7.5 · >=2.8.0 <2.8.4 · >=2.9.0 <2.9.3 · >=2.10.0 <2.10.1
- Fixed in
- 2.7.5, 2.8.4, 2.9.3, 2.10.1
Is your org.apache.pulsar:pulsar-broker version vulnerable?
- org.apache.pulsar:pulsar-broker 5.0No known advisories in 5.0.1
- org.apache.pulsar:pulsar-broker 4.2No known advisories in 4.2.5
- org.apache.pulsar:pulsar-broker 4.1No known advisories in 4.1.3
- org.apache.pulsar:pulsar-broker 4.0No known advisories in 4.0.14
- org.apache.pulsar:pulsar-broker 3.3No known advisories in 3.3.9
- org.apache.pulsar:pulsar-broker 3.2No known advisories in 3.2.4
- org.apache.pulsar:pulsar-broker 3.11 advisory in 3.1.3
- org.apache.pulsar:pulsar-broker 3.0No known advisories in 3.0.17
Which of your client projects still run an old org.apache.pulsar:pulsar-broker?
NPMscan reads the pom.xml, build.gradle and gradle.lockfile in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other Maven packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the Maven registry.