Skip to content

Apache Pulsar Brokers and Proxies vulnerable to Improper Certificate Validation

Moderate severity GitHub Reviewed Published Sep 25, 2022 to the GitHub Advisory Database • Updated Jan 29, 2023

Package

maven org.apache.pulsar:pulsar-broker (Maven)

Affected versions

< 2.7.5
>= 2.8.0, < 2.8.4
>= 2.9.0, < 2.9.3
= 2.10.0

Patched versions

2.7.5
2.8.4
2.9.3
2.10.1
maven org.apache.pulsar:pulsar-proxy (Maven)
< 2.7.5
>= 2.8.0, < 2.8.4
>= 2.9.0, < 2.9.3
= 2.10.0
2.7.5
2.8.4
2.9.3
2.10.1

Description

Apache Pulsar Brokers and Proxies create an internal Pulsar Admin Client that does not verify peer TLS certificates, even when tlsAllowInsecureConnection is disabled via configuration. The Pulsar Admin Client's intra-cluster and geo-replication HTTPS connections are vulnerable to man in the middle attacks, which could leak authentication data, configuration data, and any other data sent by these clients. 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. This issue affects Apache Pulsar Broker and 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.

References

Published by the National Vulnerability Database Sep 23, 2022
Published to the GitHub Advisory Database Sep 25, 2022
Reviewed Sep 30, 2022
Last updated Jan 29, 2023

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS score

0.046%
(18th percentile)

Weaknesses

CVE ID

CVE-2022-33683

GHSA ID

GHSA-j3qw-g67q-7m64

Source code

No known source code
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.