Skip to main content

CVE-2022-33682: CWE-295 Improper Certificate Validation in Apache Software Foundation Apache Pulsar

Medium
VulnerabilityCVE-2022-33682cvecve-2022-33682cwe-295
Published: Fri Sep 23 2022 (09/23/2022, 09:25:14 UTC)
Source: CVE Database V5
Vendor/Project: Apache Software Foundation
Product: Apache Pulsar

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.

AI-Powered Analysis

AILast updated: 07/06/2025, 04:12:24 UTC

Technical Analysis

CVE-2022-33682 is a medium-severity vulnerability affecting multiple versions of Apache Pulsar, an open-source distributed messaging and streaming platform developed by the Apache Software Foundation. The vulnerability arises from improper certificate validation (CWE-295) in the TLS hostname verification process within several Pulsar components: 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. Specifically, these clients do not properly enable or enforce TLS hostname verification for intra-cluster connections and geo-replication connections. This flaw allows an attacker positioned between the client and server (a man-in-the-middle, MITM) to present a cryptographically valid certificate for a different hostname, which the client erroneously accepts. As a result, the attacker can intercept and manipulate traffic, potentially leaking sensitive information such as credentials, configuration data, and message payloads transmitted over the pulsar+ssl protocol or HTTPS. Exploitation requires the attacker to control a network node between the communicating parties and actively manipulate the traffic. The vulnerability affects Apache Pulsar versions 2.6 and earlier, as well as versions 2.7.0 to 2.7.4, 2.8.0 to 2.8.3, 2.9.0 to 2.9.2, and 2.10.0. Although no known public exploits exist at this time, the vulnerability poses a significant risk to the confidentiality of intra-cluster and geo-replication communications in affected deployments. The CVSS v3.1 base score is 5.9 (medium), reflecting the network attack vector, no privileges required, no user interaction, and high confidentiality impact but no impact on integrity or availability.

Potential Impact

For European organizations utilizing Apache Pulsar for messaging and streaming, this vulnerability could lead to unauthorized disclosure of sensitive data within their messaging infrastructure. Since intra-cluster and geo-replication communications often carry critical operational data, credentials, and messages, a successful MITM attack could compromise confidentiality, potentially exposing business secrets, personal data, or operational commands. This risk is particularly acute for organizations with distributed Pulsar clusters spanning multiple data centers or countries, where network traffic traverses less trusted or public networks. The leakage of credentials could also facilitate further lateral movement or privilege escalation within the affected environment. While the vulnerability does not directly impact data integrity or availability, the confidentiality breach alone can have severe regulatory and reputational consequences, especially under GDPR and other European data protection laws. The requirement for an attacker to be positioned between client and server somewhat limits the attack surface but does not eliminate risk, especially in cloud or hybrid environments where network segmentation may be less strict.

Mitigation Recommendations

European organizations should immediately assess their Apache Pulsar deployments to identify affected versions (2.6 and earlier, 2.7.0-2.7.4, 2.8.0-2.8.3, 2.9.0-2.9.2, and 2.10.0). They should upgrade to the latest patched versions where TLS hostname verification is properly enforced. If immediate upgrading is not feasible, organizations should implement network-level mitigations such as strict network segmentation to limit the possibility of MITM attacks within intra-cluster and geo-replication communication paths. Deploying mutual TLS authentication with strict hostname verification policies at the network or application layer can help mitigate risks. Additionally, organizations should monitor network traffic for anomalies indicative of MITM activity and audit logs for suspicious access patterns. Employing network encryption monitoring tools and intrusion detection systems that can detect certificate anomalies or unexpected TLS handshakes is recommended. Finally, organizations should review and update their incident response plans to include scenarios involving intra-cluster communication interception.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
apache
Date Reserved
2022-06-15T00:00:00.000Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6835d30c182aa0cae216c451

Added to database: 5/27/2025, 2:58:20 PM

Last enriched: 7/6/2025, 4:12:24 AM

Last updated: 8/2/2025, 1:15:21 AM

Views: 12

Actions

PRO

Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats