cve.bz

CVE-2022-33682 apache pulsar: Improper Certificate Validation

5.9 mediumEPSS 0.7%Fix available

Medium (5.9) in apache pulsar. EPSS 0.7% estimated probability of exploitation activity in the next 30 days. Fixed in org.apache.pulsar:pulsar-broker 2.10.1, 2.7.5, 2.8.4.

On this page
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.

Severity

CVSS 3.1

5.9 medium
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS
0.7% (unchanged from 0.7% a week ago; 0.7% 30 days ago) estimated probability of exploitation activity in the next 30 days; 55th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2025-05-27. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-295 Improper Certificate Validation
OWASP Top 10
A07:2025 Authentication Failures
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2022-33682 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2022-33682?via=ask-ai-copy and https://cve.bz/cve/CVE-2022-33682?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2022-33682 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Apache Software Foundation Apache Pulsar2.10.0
Apache Software Foundation Apache Pulsarfrom 2.7 through 2.7.4
Apache Software Foundation Apache Pulsarfrom 2.8 through 2.8.3
Apache Software Foundation Apache Pulsarfrom 2.9 through 2.9.2
Apache Software Foundation Apache Pulsarfrom 2.6 and earlier through 2.6.4

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-jvf3-mfxv-jcqrMavenorg.apache.pulsar:pulsar-broker<2.7.52.7.5
GHSA-jvf3-mfxv-jcqrMavenorg.apache.pulsar:pulsar-proxy<2.7.52.7.5
GHSA-jvf3-mfxv-jcqrMavenorg.apache.pulsar:pulsar-broker>=2.8.0 <2.8.42.8.4
GHSA-jvf3-mfxv-jcqrMavenorg.apache.pulsar:pulsar-proxy>=2.8.0 <2.8.42.8.4
GHSA-jvf3-mfxv-jcqrMavenorg.apache.pulsar:pulsar-broker>=2.9.0 <2.9.32.9.3
GHSA-jvf3-mfxv-jcqrMavenorg.apache.pulsar:pulsar-proxy>=2.9.0 <2.9.32.9.3
GHSA-jvf3-mfxv-jcqrMavenorg.apache.pulsar:pulsar-broker>=2.10.0 <2.10.12.10.1
GHSA-jvf3-mfxv-jcqrMavenorg.apache.pulsar:pulsar-proxy>=2.10.0 <2.10.12.10.1

Attack patterns (CAPEC)

  • CAPEC-459 Creating a Rogue Certification Authority Certificate Likelihood: Medium · Severity: Very High
  • CAPEC-475 Signature Spoofing by Improper Validation Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON