Medium

Apache Pulsar Broker, Proxy, and WebSocket Proxy vulnerable to Improper Certificate Validation

  • Disclosed: 25.09.2022
  • Updated: 11.10.2026 11:21

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.

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
Java / Kotlin (Maven) org.apache.pulsar:pulsar-broker < 2.7.5, >= 2.8.0, < 2.8.4, >= 2.9.0, < 2.9.3, >= 2.10.0, < 2.10.1 2.7.5, 2.8.4, 2.9.3, 2.10.1
Java / Kotlin (Maven) org.apache.pulsar:pulsar-proxy < 2.7.5, >= 2.8.0, < 2.8.4, >= 2.9.0, < 2.9.3, >= 2.10.0, < 2.10.1 2.7.5, 2.8.4, 2.9.3, 2.10.1

References

CVSS score 5.9/10
CVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
Weakness (CWE)
CWE-295
Platform
Java / Kotlin (Maven)
Package
org.apache.pulsar:pulsar-broker, org.apache.pulsar:pulsar-proxy
Disclosed
25.09.2022
Updated
11.10.2026 11:21

Sources and licenses

OSV / GitHub Advisory Database - GHSA-jvf3-mfxv-jcqr - CC BY 4.0

Vulnerability history: org.apache.pulsar:pulsar-broker

All published vulnerabilities of this package (Java / Kotlin (Maven)), newest first. Shows whether this is a one-off slip or a package that needs watching.

Total entries
6
First → latest
09.2022 04.2024
Without a fix
0
Exploited in attacks
0

Severity breakdown

  • High 1
  • Medium 5

Disclosures per year

  1. 2022: 2
  2. 2023: 2
  3. 2024: 2
  4. 2025: 0
  5. 2026: 0
  1. Medium · 6.4 CVE-2024-29834 >= 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 3.0.4, 3.2.2
  2. Medium · 5.4 CVE-2024-28098 >= 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 3.2.1, 3.1.3, 3.0.3, 2.11.4, 2.10.6
  3. Medium · 6.5 CVE-2023-31007 >= 2.9.0, < 2.10.4, >= 2.11.0, < 2.11.1 2.10.4, 2.11.1
  4. High · 8.2 CVE-2023-30428 >= 2.9.0, < 2.10.4, >= 2.11.0, < 2.11.1 2.10.4, 2.11.1
  5. Medium · 5.9 CVE-2022-33683 < 2.7.5, >= 2.8.0, < 2.8.4, >= 2.9.0, < 2.9.3, >= 2.10.0, < 2.10.1 2.7.5, 2.8.4, 2.9.3, 2.10.1
  6. Apache Pulsar Broker, Proxy, and WebSocket Proxy vulnerable to Improper Certificate Validation this entry
    Medium · 5.9 CVE-2022-33682 < 2.7.5, >= 2.8.0, < 2.8.4, >= 2.9.0, < 2.9.3, >= 2.10.0, < 2.10.1 2.7.5, 2.8.4, 2.9.3, 2.10.1

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.