CVE-2022-33682 json
Disabled Hostname Verification makes Brokers, Proxies vulnerable to MITM attack
published 4y ago modified 4mo ago also GHSA-jvf3-mfxv-jcqr , EUVD-2022-6863
- cvss
- 5.9
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 54%
- public exploits
- 0
- none known
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.
Patch / fix
- maven org.apache.pulsar:pulsar-broker 2.7.5, 2.8.4, 2.9.3, 2.10.1
- maven org.apache.pulsar:pulsar-proxy 2.7.5, 2.8.4, 2.9.3, 2.10.1
- apache pulsar 2.7.5, 2.8.4, 2.9.3
Is CVE-2022-33682 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.72% chance of exploitation in the next 30 days, higher than 54% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 5.9 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N |
| NVD | 3.1 | 5.9 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N |
| CNA | 3.1 | 5.9 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N |
| GitHub | 3.1 | 5.9 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| 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 |
| 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 |
Affected products
- Apache Software Foundation Apache Pulsar
Classification
- Weakness
-
- CWE-295 Improper Certificate Validation
References
-
lists.apache.org
/thread/l0ynfl161qghwfcgbbl8ld9hzbl9t3yx
web, mailing-list, vendor-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2022-33682
advisory
Sources
- CVE List CVE-2022-33682
- GitHub Advisory GHSA-jvf3-mfxv-jcqr
- NVD CVE-2022-33682
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.