Skip to content

Proxy component of Apache Pulsar subject to abuse as Denial of Service endpoint

Moderate severity GitHub Reviewed Published Sep 25, 2022 to the GitHub Advisory Database • Updated Jan 27, 2023

Package

maven org.apache.pulsar:pulsar (Maven)

Affected versions

< 2.7.5
>= 2.8.0, < 2.8.2
>= 2.9.0, < 2.9.1

Patched versions

2.7.5
2.8.3
2.9.2

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.

References

Published by the National Vulnerability Database Sep 23, 2022
Published to the GitHub Advisory Database Sep 25, 2022
Reviewed Sep 28, 2022
Last updated Jan 27, 2023

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

EPSS score

0.056%
(25th percentile)

Weaknesses

CVE ID

CVE-2022-24280

GHSA ID

GHSA-3mg9-m3f6-v7fq

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.