Loading HuntDB...

CVE-2022-33683

UNKNOWN
Published 2022-09-23T09:25:15.000Z
Actions:

Expert Analysis

Professional remediation guidance

Get tailored security recommendations from our analyst team for CVE-2022-33683. We'll provide specific mitigation strategies based on your environment and risk profile.

CVSS Score

V3.1
5.9
/10
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
Base Score Metrics
Exploitability: N/A Impact: N/A

EPSS Score

v2025.03.14
0.001
probability
of exploitation in the wild

There is a 0.1% chance that this vulnerability will be exploited in the wild within the next 30 days.

Updated: 2025-06-25
Exploit Probability
Percentile: 0.289
Higher than 28.9% of all CVEs

Attack Vector Metrics

Attack Vector
NETWORK
Attack Complexity
HIGH
Privileges Required
NONE
User Interaction
NONE
Scope
UNCHANGED

Impact Metrics

Confidentiality
HIGH
Integrity
NONE
Availability
NONE

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.

Available Exploits

No exploits available for this CVE.

Related News

No news articles found for this CVE.

Affected Products

GitHub Security Advisories

Community-driven vulnerability intelligence from GitHub

✓ GitHub Reviewed MODERATE

Apache Pulsar Brokers and Proxies vulnerable to Improper Certificate Validation

GHSA-j3qw-g67q-7m64

Advisory Details

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.

Affected Packages

Maven org.apache.pulsar:pulsar-broker
ECOSYSTEM: ≥0 <2.7.5
Maven org.apache.pulsar:pulsar-proxy
ECOSYSTEM: ≥0 <2.7.5
Maven org.apache.pulsar:pulsar-broker
ECOSYSTEM: ≥2.8.0 <2.8.4
Maven org.apache.pulsar:pulsar-proxy
ECOSYSTEM: ≥2.8.0 <2.8.4
Maven org.apache.pulsar:pulsar-broker
ECOSYSTEM: ≥2.9.0 <2.9.3
Maven org.apache.pulsar:pulsar-proxy
ECOSYSTEM: ≥2.9.0 <2.9.3
Maven org.apache.pulsar:pulsar-broker
ECOSYSTEM: ≥2.10.0 <2.10.1
Maven org.apache.pulsar:pulsar-proxy
ECOSYSTEM: ≥2.10.0 <2.10.1

CVSS Scoring

CVSS Score

5.0

CVSS Vector

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

Advisory provided by GitHub Security Advisory Database. Published: September 25, 2022, Modified: September 30, 2022

References

Published: 2022-09-23T09:25:15.000Z
Last Modified: 2025-05-22T18:27:17.447Z
Copied to clipboard!