dbcve.org
PulsarApplication · Apache

CVE-2022-34321

HIGH · 8.2 CVSS v3.1 Published 2024-03-12
Fix available
A fix is available. Upgrade to 2.10.6 / 2.11.3 or later.
See remediation →
91/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Apache Pulsar Proxy's /proxy-stats endpoint lacks authentication, allowing unauthenticated attackers to access detailed live connection statistics (including client IPs) and modify logging levels. The logging manipulation can be exploited for denial of service by overwhelming the proxy with excessive log output.

MitigationUpgrade Pulsar Proxy to the patched version (2.10.6+, 2.11.3+, 3.0.2+, or 3.1.1+) and ensure the proxy is not directly exposed to the internet—operate within a secured network behind perimeter defenses.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
PulsarApplication
Affected:>= 2.6.0, < 2.10.6>= 2.11.0, < 2.11.3>= 3.0.0, < 3.0.2= 3.1.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Pulsar Proxy version
    Run pulsar-admin proxy-stats version or check the Pulsar distribution version in the installation directory (e.g., ls pulsar/lib/pulsar-proxy-common or check conf/proxy.conf for version info)
    Affected if The installed version falls within >= 2.6.0 and < 2.10.6, OR >= 2.11.0 and < 2.11.3, OR >= 3.0.0 and < 3.0.2, OR = 3.1.0
  2. Confirm proxy role is enabled
    Check conf/proxy.conf or conf/broker.conf for 'proxyRoles' setting, or check if the process is running as proxy using ps aux | grep pulsar-proxy
    Affected if The proxy role is enabled and the instance is acting as a Pulsar Proxy
  3. Verify /proxy-stats endpoint accessibility
    Send an unauthenticated HTTP request to the proxy-stats endpoint: curl -s http://<proxy-host>:8080/proxy-stats or port 8080/8081 depending on config
    Affected if The endpoint returns statistics (connection details, client IPs, logging configuration) without requiring authentication credentials
  4. Check network exposure
    Review firewall rules, load balancer config, or Kubernetes service definitions to determine if the proxy HTTP port (default 8080) is exposed to untrusted networks or the public internet
    Affected if The proxy HTTP port is directly accessible from untrusted networks or the internet without additional authentication or network-level access controls

You are affected if running a vulnerable Pulsar Proxy version AND the /proxy-stats endpoint is accessible without authentication from an untrusted network.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.10.6 / 2.11.3 / 3.0.2 or later
Fixed in 2.10.62.11.33.0.2
Interim mitigation

Upgrade Pulsar Proxy to the patched version (2.10.6+, 2.11.3+, 3.0.2+, or 3.1.1+) and ensure the proxy is not directly exposed to the internet—operate within a secured network behind perimeter defenses.

Recommended fix High confidence

Upgrade to 2.10.6+ (for 2.10.x branches), 2.11.3+ (for 2.11.x branches), 3.0.2+ (for 3.0.x branches), or 3.1.1+ (for 3.1.x)

  1. 1. Identify the currently running Apache Pulsar Proxy version using the Pulsar admin CLI: ` pulsar-admin versions ` or check the container/dashboard version.
  2. 2. Determine the appropriate upgrade path based on your current major version branch (2.10.x, 2.11.x, 3.0.x, or 3.1.x).
  3. 3. For 2.10.x versions: Plan upgrade from any version >= 2.6.0 and < 2.10.6 to version 2.10.6 or later.
  4. 4. For 2.11.x versions: Plan upgrade from any version >= 2.11.0 and < 2.11.3 to version 2.11.3 or later.
  5. 5. For 3.0.x versions: Plan upgrade from any version >= 3.0.0 and < 3.0.2 to version 3.0.2 or later.
  6. 6. For version 3.1.0: Plan upgrade to version 3.1.1 or later.
  7. 7. Before upgrading in production, test the new version in a staging environment to verify compatibility with your existing Pulsar cluster configuration and client applications.
  8. 8. Perform the upgrade following standard Pulsar rolling upgrade procedures, ensuring proper backup of configuration and state.
Caveat Standard Pulsar upgrade considerations apply - review release notes for any configuration or API changes between your current and target version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Pulsar Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-34321 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-34321 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data