cve.bz

CVE-2022-34321 apache pulsar

8.2 highEPSS 1.8%Fix available

High (8.2) in apache pulsar. EPSS 1.8% estimated probability of exploitation activity in the next 30 days. Fixed in org.apache.pulsar:pulsar-proxy 2.10.6, 2.11.3, 3.0.2.

On this page
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.

Severity

CVSS 3.1

8.2 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
EPSS
1.8% (unchanged from 1.8% a week ago; 1.8% 30 days ago) estimated probability of exploitation activity in the next 30 days; 79th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2024-08-13. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-306 Missing Authentication for Critical Functionality
OWASP Top 10
A07:2025 Authentication Failures
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2022-34321 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2022-34321?via=ask-ai-copy and https://cve.bz/cve/CVE-2022-34321?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2022-34321 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Apache Software Foundation Apache Pulsarfrom 2.6.0 before 2.10.6
Apache Software Foundation Apache Pulsarfrom 2.11.0 before 2.11.3
Apache Software Foundation Apache Pulsarfrom 3.0.0 before 3.0.2
Apache Software Foundation Apache Pulsarfrom 3.1.0 before 3.1.1

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-c35h-w8hj-mm55Mavenorg.apache.pulsar:pulsar-proxy>=2.6.0 <2.10.62.10.6
GHSA-c35h-w8hj-mm55Mavenorg.apache.pulsar:pulsar-proxy>=2.11.0 <2.11.32.11.3
GHSA-c35h-w8hj-mm55Mavenorg.apache.pulsar:pulsar-proxy>=3.0.0 <3.0.23.0.2
GHSA-c35h-w8hj-mm55Mavenorg.apache.pulsar:pulsar-proxy>=3.1.0 <3.1.13.1.1

Red Hat

Red Hat rates this Important.

Red Hat's statement

Apache Pulsar is not part of EAP - it's not present in the EAP dependency tree and not distributed in the product maven repository. EAP is not affected.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

ProductPackageStateAdvisory
Red Hat build of Apache Camel for Spring Boot 3apache-pulsarNot affected
Red Hat build of Apache Camel for Spring Boot 4apache-pulsarNot affected
Red Hat Fuse 7apache-pulsarAffected
Red Hat Integration Camel K 1apache-pulsarNot affected
Red Hat JBoss Enterprise Application Platform 8pulsar-proxyNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2022-34321.

Attack patterns (CAPEC)

  • CAPEC-12 Choosing Message Identifier Likelihood: High · Severity: High
  • CAPEC-36 Using Unpublished Interfaces or Functionality Likelihood: Medium · Severity: High
  • CAPEC-62 Cross Site Request Forgery Likelihood: High · Severity: Very High
  • CAPEC-166 Force the System to Reset Values Severity: Medium
  • CAPEC-216 Communication Channel Manipulation

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON