CVE-2022-34321
What it is
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.
At a glance
- Exploitability
- Can be exploited over the network without logging in. High risk of data exposure.
- Exploit odds
- 1.8% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 1.8% in the next 30 days (EPSS).
- Severity: 8.2 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 1.8% · EPSS, next 30 days
- Weakness
- CWE-306 · Missing authentication
- Record status
- Analyzed
Affected
- Apache Pulsar < 2.10.6
- Apache Pulsar < 2.11.3
- Apache Pulsar < 3.0.2
- Apache Pulsar 3.1.0
Attack profile CVSS 3.1 · 8.2
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- Low
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:L
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2022-34321.md and follow it. Check whether this project is affected by CVE-2022-34321. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://lists.apache.org/thread/ods5tq2hpl390hvjnvxv0bcg4rfpgjj8
- https://pulsar.apache.org/security/CVE-2022-34321/
- https://lists.apache.org/thread/ods5tq2hpl390hvjnvxv0bcg4rfpgjj8
- https://pulsar.apache.org/security/CVE-2022-34321/
References
- http://www.openwall.com/lists/oss-security/2024/03/12/8
- https://lists.apache.org/thread/ods5tq2hpl390hvjnvxv0bcg4rfpgjj8
- https://pulsar.apache.org/security/CVE-2022-34321/
- http://www.openwall.com/lists/oss-security/2024/03/12/8
- https://lists.apache.org/thread/ods5tq2hpl390hvjnvxv0bcg4rfpgjj8
- https://pulsar.apache.org/security/CVE-2022-34321/