Disabled Hostname Verification makes Brokers, Proxies vulnerable to MITM attack
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- High
- Impact type
- Spoofing
- Confidentiality · integrity · availability
- High · None · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CISA ADP. Fix status from CNA and GitHub. Impact type from CWE-295.
Summary
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| Apache | Apache Pulsar | 2.10.0; 2.7 – 2.7.4; 2.8 – 2.8.3; 2.9 – 2.9.2; 2.6 and earlier – 2.6.4 | — | No fix listed | CNA |
| — | org.apache.pulsar:pulsar-broker (Maven) | before 2.7.5 | 2.7.5 | Patch available | GHSA-jvf3-mfxv-jcqr |
| — | org.apache.pulsar:pulsar-proxy (Maven) | before 2.7.5 | 2.7.5 | Patch available | GHSA-jvf3-mfxv-jcqr |
| — | org.apache.pulsar:pulsar-broker (Maven) | 2.8.0 to before 2.8.4 | 2.8.4 | Patch available | GHSA-jvf3-mfxv-jcqr |
| — | org.apache.pulsar:pulsar-proxy (Maven) | 2.8.0 to before 2.8.4 | 2.8.4 | Patch available | GHSA-jvf3-mfxv-jcqr |
| — | org.apache.pulsar:pulsar-broker (Maven) | 2.9.0 to before 2.9.3 | 2.9.3 | Patch available | GHSA-jvf3-mfxv-jcqr |
| — | org.apache.pulsar:pulsar-proxy (Maven) | 2.9.0 to before 2.9.3 | 2.9.3 | Patch available | GHSA-jvf3-mfxv-jcqr |
| — | org.apache.pulsar:pulsar-broker (Maven) | 2.10.0 to before 2.10.1 | 2.10.1 | Patch available | GHSA-jvf3-mfxv-jcqr |
| — | org.apache.pulsar:pulsar-proxy (Maven) | 2.10.0 to before 2.10.1 | 2.10.1 | Patch available | GHSA-jvf3-mfxv-jcqr |
- Apache Pulsar VendorApache Affected 2.10.0; 2.7 – 2.7.4; 2.8 – 2.8.3; 2.9 – 2.9.2; 2.6 and earlier – 2.6.4 Fixed in — No fix listed CNA
- org.apache.pulsar:pulsar-broker (Maven) Vendor— Affected before 2.7.5 Fixed in 2.7.5 Patch available GHSA-jvf3-mfxv-jcqr
- org.apache.pulsar:pulsar-proxy (Maven) Vendor— Affected before 2.7.5 Fixed in 2.7.5 Patch available GHSA-jvf3-mfxv-jcqr
- org.apache.pulsar:pulsar-broker (Maven) Vendor— Affected 2.8.0 to before 2.8.4 Fixed in 2.8.4 Patch available GHSA-jvf3-mfxv-jcqr
- org.apache.pulsar:pulsar-proxy (Maven) Vendor— Affected 2.8.0 to before 2.8.4 Fixed in 2.8.4 Patch available GHSA-jvf3-mfxv-jcqr
- org.apache.pulsar:pulsar-broker (Maven) Vendor— Affected 2.9.0 to before 2.9.3 Fixed in 2.9.3 Patch available GHSA-jvf3-mfxv-jcqr
- org.apache.pulsar:pulsar-proxy (Maven) Vendor— Affected 2.9.0 to before 2.9.3 Fixed in 2.9.3 Patch available GHSA-jvf3-mfxv-jcqr
- org.apache.pulsar:pulsar-broker (Maven) Vendor— Affected 2.10.0 to before 2.10.1 Fixed in 2.10.1 Patch available GHSA-jvf3-mfxv-jcqr
- org.apache.pulsar:pulsar-proxy (Maven) Vendor— Affected 2.10.0 to before 2.10.1 Fixed in 2.10.1 Patch available GHSA-jvf3-mfxv-jcqr
Remediation
- Fix · GHSA-jvf3-mfxv-jcqr org.apache.pulsar:pulsar-broker (Maven) Fixed in 2.7.5 Advisory →
- Fix · GHSA-jvf3-mfxv-jcqr org.apache.pulsar:pulsar-proxy (Maven) Fixed in 2.7.5 Advisory →
- Fix · GHSA-jvf3-mfxv-jcqr org.apache.pulsar:pulsar-broker (Maven) Fixed in 2.8.4 Advisory →
- Fix · GHSA-jvf3-mfxv-jcqr org.apache.pulsar:pulsar-proxy (Maven) Fixed in 2.8.4 Advisory →
- Fix · GHSA-jvf3-mfxv-jcqr org.apache.pulsar:pulsar-broker (Maven) Fixed in 2.9.3 Advisory →
- Fix · GHSA-jvf3-mfxv-jcqr org.apache.pulsar:pulsar-proxy (Maven) Fixed in 2.9.3 Advisory →
- Fix · GHSA-jvf3-mfxv-jcqr org.apache.pulsar:pulsar-broker (Maven) Fixed in 2.10.1 Advisory →
- Fix · GHSA-jvf3-mfxv-jcqr org.apache.pulsar:pulsar-proxy (Maven) Fixed in 2.10.1 Advisory →
Timeline
- 2026-10-02 Threatist record created from CVE-2022-33682
- 2026-10-03 Alias added: GHSA-jvf3-mfxv-jcqr
References
More Apache Pulsar vulnerabilities
- TI-2024-18155 Apache Pulsar: Pulsar Functions Worker's Archive Extraction Vulnerability Allows Unauthorized File Modification CVSS 3.1CRITICAL 9.9
- TI-2021-05150 Authentication with JWT allows use of “none”-algorithm CVSS 3.1CRITICAL 9.8
- TI-2024-17990 Apache Pulsar: Improper Input Validation in Pulsar Function Worker allows Remote Code Execution CVSS 3.1CRITICAL 9.9
- TI-2023-14272 Apache Pulsar: Incorrect Authorization for Function Worker when using mTLS Authentication through Pulsar Proxy CVSS 3.1CRITICAL 9.6
- TI-2022-15232 Apache Pulsar: Improper Authentication for Pulsar Proxy Statistics Endpoint CVSS 3.1HIGH 8.2
- TI-2024-18500 Apache Pulsar: Pulsar Functions Worker Allows Unauthorized File Access and Unauthorized HTTP/HTTPS Proxying CVSS 3.1HIGH 8.8
Sources
- CVE-2022-33682 · CVE Program
- CVE-2022-33682 · NVD
- FIRST EPSS
- GHSA-jvf3-mfxv-jcqr · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences