CVE-2022-24280

Apache Pulsar Proxy target broker address isn't validated

Description

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.

Remediation

Workaround:

  • To address the issue, upgraded versions of Apache Pulsar Proxy will only allow connections to known broker ports 6650 and 6651 by default. In addition, it is necessary to limit proxied broker connections further to known broker addresses by specifying brokerProxyAllowedHostNames and brokerProxyAllowedIPAddresses Pulsar Proxy settings. In Pulsar Helm chart deployments, the setting names should be prefixed with "PULSAR_PREFIX_". 2.7 users should upgrade Pulsar Proxies to 2.7.5 and apply configuration changes. 2.8 users should upgrade Pulsar Proxies to at least 2.8.3 and apply configuration changes. 2.9 users should upgrade Pulsar Proxies to at least 2.9.2 and apply configuration changes. 2.10 users should apply configuration changes. Any users running the Pulsar Proxy 2.6.4 and earlier should upgrade to one of the above patched versions and apply configuration changes.

Category

6.5
CVSS
Severity: Medium
CVSS 3.1 •
EPSS 0.03%
Vendor Advisory apache.org
Affected: Apache Software Foundation Apache Pulsar
Published at:
Updated at:

References

Link Tags
https://lists.apache.org/thread/ghs9jtjfbpy4c6xcftyvkl6swznlom1v mailing list vendor advisory

Frequently Asked Questions

What is the severity of CVE-2022-24280?
CVE-2022-24280 has been scored as a medium severity vulnerability.
How to fix CVE-2022-24280?
As a workaround for remediating CVE-2022-24280: To address the issue, upgraded versions of Apache Pulsar Proxy will only allow connections to known broker ports 6650 and 6651 by default. In addition, it is necessary to limit proxied broker connections further to known broker addresses by specifying brokerProxyAllowedHostNames and brokerProxyAllowedIPAddresses Pulsar Proxy settings. In Pulsar Helm chart deployments, the setting names should be prefixed with "PULSAR_PREFIX_". 2.7 users should upgrade Pulsar Proxies to 2.7.5 and apply configuration changes. 2.8 users should upgrade Pulsar Proxies to at least 2.8.3 and apply configuration changes. 2.9 users should upgrade Pulsar Proxies to at least 2.9.2 and apply configuration changes. 2.10 users should apply configuration changes. Any users running the Pulsar Proxy 2.6.4 and earlier should upgrade to one of the above patched versions and apply configuration changes.
Is CVE-2022-24280 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2022-24280 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2022-24280?
CVE-2022-24280 affects Apache Software Foundation Apache Pulsar.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.