Summary
Apache Pulsar Broker, Proxy, and WebSocket Proxy vulnerable to Improper Certificate Validation
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.
Impact
CVE-2022-33682 has a CVSS score of 5.9 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.7.5, 2.8.4, 2.9.3, 2.10.1); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
org.apache.pulsar:pulsar-broker to 2.7.5 or later; org.apache.pulsar:pulsar-proxy to 2.7.5 or later; org.apache.pulsar:pulsar-broker to 2.8.4 or later; org.apache.pulsar:pulsar-proxy to 2.8.4 or later; org.apache.pulsar:pulsar-broker to 2.9.3 or later; org.apache.pulsar:pulsar-proxy to 2.9.3 or later; org.apache.pulsar:pulsar-broker to 2.10.1 or later; org.apache.pulsar:pulsar-proxy to 2.10.1 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2022-33682? CVE-2022-33682 is a medium-severity security vulnerability in org.apache.pulsar:pulsar-broker (maven), affecting versions < 2.7.5. It is fixed in 2.7.5, 2.8.4, 2.9.3, 2.10.1.
- How severe is CVE-2022-33682? CVE-2022-33682 has a CVSS score of 5.9 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which packages are affected by CVE-2022-33682?
org.apache.pulsar:pulsar-broker(maven) (versions < 2.7.5)org.apache.pulsar:pulsar-proxy(maven) (versions < 2.7.5)
- Is there a fix for CVE-2022-33682? Yes. CVE-2022-33682 is fixed in 2.7.5, 2.8.4, 2.9.3, 2.10.1. Upgrade to this version or later.
- Is CVE-2022-33682 exploitable, and should I be worried? Whether CVE-2022-33682 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2022-33682 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2022-33682?
- Upgrade
org.apache.pulsar:pulsar-brokerto 2.7.5 or later - Upgrade
org.apache.pulsar:pulsar-proxyto 2.7.5 or later - Upgrade
org.apache.pulsar:pulsar-brokerto 2.8.4 or later - Upgrade
org.apache.pulsar:pulsar-proxyto 2.8.4 or later - Upgrade
org.apache.pulsar:pulsar-brokerto 2.9.3 or later - Upgrade
org.apache.pulsar:pulsar-proxyto 2.9.3 or later - Upgrade
org.apache.pulsar:pulsar-brokerto 2.10.1 or later - Upgrade
org.apache.pulsar:pulsar-proxyto 2.10.1 or later
- Upgrade