CVE-2022-33682
Last modified
CVE-2022-33682 is a medium-severity vulnerability rated 5.9/10 on the CVSS scale. 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. EPSS estimates a 0.58% chance of exploitation in the next 30 days.
Description
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.
Metrics
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Apache | Pulsar | < 2.7.5 |
| Apache | Pulsar | >= 2.8.0, < 2.8.4 |
| Apache | Pulsar | >= 2.9.0, < 2.9.3 |
| Apache | Pulsar | 2.10.0 |
References
- https://lists.apache.org/thread/l0ynfl161qghwfcgbbl8ld9hzbl9t3yxMailing List, Vendor Advisory
- https://lists.apache.org/thread/l0ynfl161qghwfcgbbl8ld9hzbl9t3yxMailing List, Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2022-33682?
How severe is CVE-2022-33682?
How do I fix CVE-2022-33682?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2022
- CVE-2022-33677Azure Site Recovery Elevation of Privilege Vulnerability7.2
- CVE-2022-33678Azure Site Recovery Remote Code Execution Vulnerability7.2
- CVE-2022-33679Windows Kerberos Elevation of Privilege Vulnerability8.1
- CVE-2022-3368A vulnerability within the Software Updater functionality of…8.8
- CVE-2022-33680Microsoft Edge (Chromium-based) Elevation of Privilege Vulne…8.3
- CVE-2022-33681Delayed TLS hostname verification in the Pulsar Java Client …5.9
- CVE-2022-33683Apache Pulsar Brokers and Proxies create an internal Pulsar …5.9
- CVE-2022-33684The Apache Pulsar C++ Client does not verify peer TLS certif…8.1
- CVE-2022-33685Unprotected dynamic receiver in Wearable Manager Service pri…5.5
- CVE-2022-33686Exposure of Sensitive Information in GsmAlarmManager prior t…2.3
- CVE-2022-33687Exposure of Sensitive Information in telephony-common.jar pr…3.3
- CVE-2022-33688Sensitive information exposure vulnerability in EventType in…3.3
Are you affected by CVE-2022-33682?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
