8.2

CVE-2022-34321: apache software foundation apache pulsar

CVSS: 8.2v3.1HighAnalyzed
AliasesGHSA-c35h-w8hj-mm55
Published 12-03-2024Last modified 13-02-2025

Vulnerability summary

CVE-2022-34321 is a high (CVSS 8.2) vulnerability in apache software foundation apache pulsar. EPSS estimates a 1.76% chance of exploitation in the next 30 days, higher than 77.6% of scored vulnerabilities.

Overall risk
33/100
0100
Medium · default modelHow is this calculated?
CVSS score
8.2/10
010
High · v3.1 (CVE.org)
EPSS score
1.76%
0%100%
Low · 0.00 pp in 30 days
KEVNot listedIn no KEV catalog
RansomwareNone recordedNo known use recorded
Public exploits0No public exploits recorded

Timeline

  1. 12-03-2024
    PublishedVulnerability first disclosed.
  2. 13-02-2025
    Last modifiedVulnerability information updated.

Description

Improper Authentication vulnerability in Apache Pulsar Proxy allows an attacker to connect to the /proxy-stats endpoint without authentication. The vulnerable endpoint exposes detailed statistics about live connections, along with the capability to modify the logging level of proxied connections without requiring proper authentication credentials. This issue affects Apache Pulsar versions from 2.6.0 to 2.10.5, from 2.11.0 to 2.11.2, from 3.0.0 to 3.0.1, and 3.1.0. The known risks include exposing sensitive information such as connected client IP and unauthorized logging level manipulation which could lead to a denial-of-service condition by significantly increasing the proxy's logging overhead. When deployed via the Apache Pulsar Helm chart within Kubernetes environments, the actual client IP might not be revealed through the load balancer's default behavior, which typically obscures the original source IP addresses when externalTrafficPolicy is being configured to "Cluster" by default. The /proxy-stats endpoint contains topic level statistics, however, in the default configuration, the topic level statistics aren't known to be exposed. 2.10 Pulsar Proxy users should upgrade to at least 2.10.6. 2.11 Pulsar Proxy users should upgrade to at least 2.11.3. 3.0 Pulsar Proxy users should upgrade to at least 3.0.2. 3.1 Pulsar Proxy users should upgrade to at least 3.1.1. Users operating versions prior to those listed above should upgrade to the aforementioned patched versions or newer versions. Additionally, it's imperative to recognize that the Apache Pulsar Proxy is not intended for direct exposure to the internet. The architectural design of Pulsar Proxy assumes that it will operate within a secured network environment, safeguarded by appropriate perimeter defenses.

CVSS metrics

3 scores · 3 sources · 1 version

EPSS trend

Probability

1.76%

Chance of exploitation in the next 30 days

Percentile

78%

Versus all other CVEs

30-day change

0.00 pp

From 1.76% on 18-09-2026

18-09-202618-10-2026
EPSS score
1.76%

Known exploited

Compare KEV catalogs

Not in any of the 3 tracked catalogs.

Public exploits

0 found

No public exploits indexed.

Weaknesses

CWE · root cause

Affected systems

Apache1 product
  • pulsarEOL≥ 2.6.0, < 2.10.6 | ≥ 2.11.0, < 2.11.3 | ≥ 3.0.0, < 3.0.2 | 3.1.0
Apache software foundation1 product
  • apache pulsar≥ 2.6.0, < 2.10.6 | ≥ 2.11.0, < 2.11.3 | ≥ 3.0.0, < 3.0.2 | ≥ 3.1.0, < 3.1.1
Org.apache.pulsar1 product
  • pulsar-proxy≥ 2.6.0, < 2.10.6 | ≥ 2.11.0, < 2.11.3 | ≥ 3.0.0, < 3.0.2 | ≥ 3.1.0, < 3.1.1

3 vendors · 3 products

References

6 links