high
8.2
CWE
306
Advisory Published
CVE Published
Advisory Published
Updated

CVE-2022-34321: Apache Pulsar: Improper Authentication for Pulsar Proxy Statistics Endpoint

First published: Tue Mar 12 2024(Updated: )

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.

Credit: security@apache.org security@apache.org

Affected SoftwareAffected VersionHow to fix
maven/org.apache.pulsar:pulsar-proxy>=3.1.0<3.1.1
3.1.1
maven/org.apache.pulsar:pulsar-proxy>=3.0.0<=3.0.1
3.0.2
maven/org.apache.pulsar:pulsar-proxy>=2.11.0<=2.11.2
2.11.3
maven/org.apache.pulsar:pulsar-proxy>=2.6.0<=2.10.5
2.10.6
Apache Pulsar>=2.6.0<2.10.6
Apache Pulsar>=2.11.0<2.11.3
Apache Pulsar>=3.0.0<3.0.2
Apache Pulsar=3.1.0

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

Reference Links

Frequently Asked Questions

  • What is the severity of CVE-2022-34321?

    CVE-2022-34321 is classified as a high severity vulnerability affecting Apache Pulsar Proxy.

  • How do I fix CVE-2022-34321?

    To fix CVE-2022-34321, upgrade to Apache Pulsar Proxy version 3.1.1, 3.0.2, 2.11.3, or 2.10.6.

  • What endpoints are affected by CVE-2022-34321?

    CVE-2022-34321 affects the /proxy-stats endpoint, which can be accessed without authentication.

  • What information does CVE-2022-34321 expose?

    CVE-2022-34321 exposes detailed statistics about live connections and allows modification of logging levels.

  • Which versions of Apache Pulsar are vulnerable to CVE-2022-34321?

    Vulnerable versions of Apache Pulsar include 3.1.0, 3.0.1, 2.11.2, and 2.10.5.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203