Safeguard
Vulnerability Analysis•

CVE-2022-34321: High Auth Flaw in Apache Pulsar Proxy

CVE-2022-34321 is a high (8.2) missing authentication flaw on the Apache Pulsar Proxy stats endpoint. Upgrade to 2.10.6, 2.11.3, 3.0.2 or 3.1.1 or newer.

Safeguard Security Team
4 min read

CVE-2022-34321 is a high severity (CVSS 8.2) improper authentication flaw in the Apache Pulsar Proxy. Its stats endpoint answers without credentials and can change logging levels. Upgrade to at least 2.10.6, 2.11.3, 3.0.2 or 3.1.1, and keep the proxy off the public internet.

What's affected

The Apache advisory lists these affected releases of the Pulsar Proxy:

  • 2.6.0 up to and including 2.10.5
  • 2.11.0 up to and including 2.11.2
  • 3.0.0 up to and including 3.0.1
  • 3.1.0

The fixed releases are 2.10.6, 2.11.3, 3.0.2 and 3.1.1. Users on older lines should move to one of those or to a newer release. The record scores the flaw 8.2 (High) with vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:L and classifies it as CWE-306 (Missing Authentication for Critical Function). Apache's own wording is improper authentication, so you will see both labels.

How to check if you're exposed

Work out which proxy version you run. In a binary distribution the version is part of the jar names in the lib directory, and in containers it is the image tag. In Kubernetes you can list the image tags in use:

kubectl get pods -A -o jsonpath='{range .items[*]}{.metadata.name}{"\t"}{.spec.containers[*].image}{"\n"}{end}' | grep -i pulsar

Then ask a second question: who can reach the proxy's HTTP port? Apache states that the Pulsar Proxy is not meant to face the internet and assumes a secured network. If a load balancer, ingress or firewall rule exposes the proxy web port broadly, treat this as urgent even before you patch.

What to do now

  1. Upgrade the proxy to 2.10.6, 2.11.3, 3.0.2, 3.1.1 or newer, matching your current release line.
  2. Restrict network access to the proxy so that only the clients and operators that need it can connect. Do not publish it to the internet.
  3. Review proxy logs for unexpected log level changes or a sudden jump in log volume, since the advisory names logging overhead as a denial of service route.
  4. If you deploy with the Apache Pulsar Helm chart, note the advisory's remark that the load balancer may hide the real client IP, which makes any exposure harder to audit after the fact.
  5. Add the version check to your inventory so the next Pulsar advisory is a lookup, not a hunt.

Why it matters

The proxy exposes a statistics endpoint at /proxy-stats. In the affected versions it did not require authentication, so anyone who could reach it could read detailed statistics about live connections, including connected client IP addresses, and could change the logging level of proxied connections. That is the textbook shape of a missing authentication check on a sensitive function.

The impact Apache describes is limited but real. Leaked client addresses help an attacker map who talks to your messaging layer. Raising log verbosity can bleed disk and CPU on the proxy and lead to denial of service. Apache also notes that topic level statistics are not known to be exposed in the default configuration. The CVE is not listed in the CISA Known Exploited Vulnerabilities catalog, and the advisory does not report exploitation.

Try it yourself

Click through it at your own pace, or open it full screen.

Quick check

Does this let someone read my message data?

The advisory does not say so. It describes exposure of connection statistics, including client IPs, and the ability to change logging levels. It adds that topic level statistics are not known to be exposed in the default configuration. Verify your own configuration.

Is a firewall enough instead of upgrading?

Network restriction is the control Apache's design assumes, and you should have it. Upgrading removes the flaw itself, so do both.

Sources

Safeguard can help you see this across many sites or repositories at once. Paste a manifest into the free in-browser dependency scan at gold.safeguard.sh/scan or look the issue up in the Gold directory to see how the record is tracked.

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

We email you a link to confirm, and only then add you to the list. Unsubscribe in one click. Privacy

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.