dbcve.org
PulsarApplication · Apache

CVE-2022-24280

MEDIUM · 6.5 CVSS v3.1 Published 2022-09-23
Fix available
A fix is available. Upgrade to 2.7.5 / 2.8.3 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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 Input Validation vulnerability in Proxy component of Apache Pulsar allows an attacker to make TCP/IP connection attempts that originate from the Pulsar Proxy's IP address. When the Apache Pulsar Proxy component is used, it is possible to attempt to open TCP/IP connections to any IP address and port that the Pulsar Proxy can connect to. An attacker could use this as a way for DoS attacks that originate from the Pulsar Proxy's IP address. It hasn’t been detected that the Pulsar Proxy authentication can be bypassed. The attacker will have to have a valid token to a properly secured Pulsar Proxy. This issue affects Apache Pulsar Proxy versions 2.7.0 to 2.7.4; 2.8.0 to 2.8.2; 2.9.0 to 2.9.1; 2.6.4 and earlier.

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

Improper input validation in Apache Pulsar Proxy allows authenticated attackers with valid tokens to trigger outbound TCP/IP connections from the proxy's IP address to arbitrary IPs and ports. This enables the proxy to be used as a bounce point for DoS amplification attacks.

MitigationUpgrade Apache Pulsar Proxy to a patched version (beyond 2.7.4, 2.8.2, 2.9.1, or 2.6.4) that addresses the input validation vulnerability in the proxy component.

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.4>= 2.7.0, < 2.7.5>= 2.8.0, < 2.8.3>= 2.9.0, < 2.9.2

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

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 installation and version
    Locate the Pulsar installation directory (common paths include /opt/apache-pulsar, /usr/local/pulsar, or a custom deployment directory). Run the command 'bin/pulsar version' or check the version file in the installation to determine the exact Pulsar version installed.
    Affected if The installed version falls within any of these ranges: <= 2.6.4; >= 2.7.0 and < 2.7.5; >= 2.8.0 and < 2.8.3; >= 2.9.0 and < 2.9.2.
  2. Verify the Pulsar Proxy component is in use
    Check if the Pulsar Proxy service is deployed and running. Look for proxy-related configuration files (such as proxy.conf or standaloneProxy.conf) and confirm the proxy process is active. Common indicators include a running 'pulsar proxy' process or proxy service status.
    Affected if The Pulsar Proxy component is deployed and running as a standalone proxy or embedded proxy in the environment.
  3. Confirm authentication is enforced on the proxy
    Examine the authentication configuration for the proxy. Check proxy.conf or the authentication settings section for properties like 'authenticationEnabled', 'authenticationProviders', or 'authorizationEnabled'. Verify whether a valid token or authentication mechanism is required to connect to the proxy.
    Affected if Authentication is disabled or set to optional on the proxy (authenticationEnabled=false or no auth provider configured), making it easier for attackers to obtain valid tokens or bypass auth checks.
  4. Check for custom or restrictive network policies
    Review any firewall rules, network policies, or Pulsar configuration that restricts outbound TCP connections initiated by the proxy. Look for configurations controlling 'connectHosts', 'allowedProxyHosts', or similar outbound connection settings in the proxy configuration.
    Affected if No network restrictions are configured on the proxy, allowing arbitrary outbound TCP connections from the proxy's IP address.

You are affected if the Pulsar Proxy is running and the installed version is within the vulnerable ranges AND the proxy accepts authenticated connections without additional outbound connection restrictions.

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.7.5 / 2.8.3 / 2.9.2 or later
Fixed in 2.7.52.8.32.9.2
Interim mitigation

Upgrade Apache Pulsar Proxy to a patched version (beyond 2.7.4, 2.8.2, 2.9.1, or 2.6.4) that addresses the input validation vulnerability in the proxy component.

Recommended fix High confidence

Upgrade to Pulsar 2.9.2 or later (latest stable 2.x release recommended)

  1. 1. Identify the currently running Apache Pulsar Proxy version using pulsar-admin or checking the deployed artifacts
  2. 2. Determine which version branch you are on (2.6.x, 2.7.x, 2.8.x, or 2.9.x)
  3. 3. For version 2.6.4 and earlier: upgrade to at least Pulsar 2.7.5 or later
  4. 4. For version 2.7.0-2.7.4: upgrade to Pulsar 2.7.5 or later
  5. 5. For version 2.8.0-2.8.2: upgrade to Pulsar 2.8.3 or later
  6. 6. For version 2.9.0-2.9.1: upgrade to Pulsar 2.9.2 or later
  7. 7. Review Apache Pulsar release notes for the target version to check for any required configuration changes
  8. 8. Test the upgrade in a staging environment before deploying to production
Caveat Review release notes for any configuration or migration steps required between versions

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

Fix this in Pulsar Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-24280 — 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-24280 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