Skip to content
Fencer Intel
high 8.2

CVE-2022-34321 json

Apache Pulsar: Improper Authentication for Pulsar Proxy Statistics Endpoint

published 2y ago modified 4mo ago also EUVD-2024-0895 , GHSA-c35h-w8hj-mm55

cvss
8.2
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.8%
EPSS 1.8% chance of exploitation in 30 days, percentile 78%
public exploits
0
none known

Summary

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.

Patch / fix

  • maven org.apache.pulsar:pulsar-proxy 2.10.6, 2.11.3, 3.0.2, 3.1.1
  • Apache Software Foundation Apache Pulsar 2.10.6, 2.11.3, 3.0.2, 3.1.1
  • apache pulsar 2.10.6, 2.11.3, 3.0.2, 3.1.1

Is CVE-2022-34321 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2022-34321 updated cvss 8.2

apache-pulsar: Improper Authentication for Pulsar Proxy Statistics Endpoint

  • Red Hat Fuse 7 apache-pulsar apache-pulsar
    affected: workaround, no fix available
  • Red Hat build of Apache Camel for Spring Boot 3 apache-pulsar apache-pulsar Red Hat build of Apache Camel for Spring Boot 4 apache-pulsar apache-pulsar Red Hat Integration Camel K 1 apache-pulsar apache-pulsar Red Hat JBoss Enterprise Application Platform 8 pulsar-proxy
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
2y ago

Exploit prediction

1.77% chance of exploitation in the next 30 days, higher than 78% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 8.2 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:L
GitHub 3.1 8.2 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
NVD 3.1 8.2 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N

Affected packages

ecosystem package affected fixed in
maven org.apache.pulsar: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
2.10.6
2.11.3
3.0.2
3.1.1

Affected products

  • Apache Software Foundation Apache Pulsar
  • apache pulsar

Classification

Weakness
  • CWE-306 Missing Authentication for Critical Functionality

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.