NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
MEDIUM severity

CVE-2022-33683 — pulsar-broker

MEDIUM

CVE-2022-33683 is a medium-severity (CVSS 5.9) CWE-295 vulnerability in org.apache.pulsar:pulsar-broker. A fix is available for org.apache.pulsar:pulsar-broker — see the affected versions and patch details below.

Disabled Certificate Validation makes Broker, Proxy Admin Clients vulnerable to MITM attack

Also known asGHSA-j3qw-g67q-7m64
Published
Updated
Affected
8 pkgs
Patched
8 / 8
Exploits
None indexed
Exploitation data as of Nov 4, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2022-33683.

EPSS Exploitation Probability

via FIRST.org ↗
0.7%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs53th percentile — riskier than 53% of all scored CVEsHighest risk
0.00%0.39%0.79%1.18%0.2%0.7%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

8 pkgs affected
☕org.apache.pulsar:pulsar-broker☕org.apache.pulsar:pulsar-proxy☕org.apache.pulsar:pulsar-broker☕org.apache.pulsar:pulsar-proxy☕org.apache.pulsar:pulsar-broker☕org.apache.pulsar:pulsar-proxy☕org.apache.pulsar:pulsar-broker☕org.apache.pulsar:pulsar-proxy

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Apache Pulsar Brokers and Proxies create 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. This issue affects Apache Pulsar Broker and 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 Packages

8 total 8 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.apache.pulsar:pulsar-brokerall versions2.7.5org.apache.pulsar:pulsar-broker:2.7.5
☕Mavenorg.apache.pulsar:pulsar-proxyall versions2.7.5org.apache.pulsar:pulsar-proxy:2.7.5
☕Mavenorg.apache.pulsar:pulsar-broker≥ 2.8.0&&< 2.8.42.8.4org.apache.pulsar:pulsar-broker:2.8.4
☕Mavenorg.apache.pulsar:pulsar-proxy≥ 2.8.0&&< 2.8.42.8.4org.apache.pulsar:pulsar-proxy:2.8.4
☕Mavenorg.apache.pulsar:pulsar-broker≥ 2.9.0&&< 2.9.32.9.3org.apache.pulsar:pulsar-broker:2.9.3
☕Mavenorg.apache.pulsar:pulsar-proxy≥ 2.9.0&&< 2.9.32.9.3org.apache.pulsar:pulsar-proxy:2.9.3

Affected Products

1 product · 4 configurations
Application
pulsarapache
≥ 2.9.0 && < 2.9.3
1 version
2.10.0

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.pulsar:pulsar-broker, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update org.apache.pulsar:pulsar-broker to 2.7.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-33683 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

Apache Pulsar Brokers and Proxies create 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
O3 Security · Impact-Aware SCA

Is CVE-2022-33683 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2022-33683: pulsar-broker — Fixed in 2.7.5