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

                							

                <!--X-Body-Begin-->
<!--X-User-Header-->

oss-sec
mailing list archives
<!--X-User-Header-End-->
<!--X-TopPNI-->

By Date

By Thread

</form>

<!--X-TopPNI-End-->
<!--X-MsgBody-->
<!--X-Subject-Header-Begin-->
CVE-2022-34321: Apache Pulsar: Improper Authentication for Pulsar Proxy Statistics Endpoint

<!--X-Subject-Header-End-->
<!--X-Head-of-Message-->

From: Lari Hotari &lt;lhotari () apache org&gt;

Date: Tue, 12 Mar 2024 16:27:19 +0000

<!--X-Head-of-Message-End-->
<!--X-Head-Body-Sep-Begin-->

<!--X-Head-Body-Sep-End-->
<!--X-Body-of-Message-->
Affected versions:

- Apache Pulsar 2.6.0 before 2.10.6
- Apache Pulsar 2.11.0 before 2.11.3
- Apache Pulsar 3.0.0 before 3.0.2
- Apache Pulsar 3.1.0 before 3.1.1

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.

Credit:

Lari Hotari (finder)

References:

https://pulsar.apache.org/
https://www.cve.org/CVERecord?id=CVE-2022-34321

<!--X-Body-of-Message-End-->
<!--X-MsgBody-End-->
<!--X-Follow-Ups-->

<!--X-Follow-Ups-End-->
<!--X-References-->
<!--X-References-End-->
<!--X-BotPNI-->

By Date

By Thread

Current thread:

CVE-2022-34321: Apache Pulsar: Improper Authentication for Pulsar Proxy Statistics Endpoint Lari Hotari (Mar 12)

<!--X-BotPNI-End-->
<!--X-User-Footer-->
<!--X-User-Footer-End-->