Skip to content

Apache Pulsar: Improper Authorization For Topic-Level Policy Management

Moderate severity GitHub Reviewed Published Mar 12, 2024 to the GitHub Advisory Database • Updated May 2, 2024

Package

maven org.apache.pulsar:pulsar-broker (Maven)

Affected versions

>= 3.2.0, < 3.2.1
>= 3.1.0, <= 3.1.2
>= 3.0.0, <= 3.0.2
>= 2.11.0, <= 2.11.3
>= 2.7.1, <= 2.10.5

Patched versions

3.2.1
3.1.3
3.0.3
2.11.4
2.10.6

Description

The vulnerability allows authenticated users with only produce or consume permissions to modify topic-level policies, such as retention, TTL, and offloading settings. These management operations should be restricted to users with the tenant admin role or super user role.

This issue affects Apache Pulsar versions from 2.7.1 to 2.10.5, from 2.11.0 to 2.11.3, from 3.0.0 to 3.0.2, from 3.1.0 to 3.1.2, and 3.2.0.

2.10 Apache Pulsar users should upgrade to at least 2.10.6.
2.11 Apache Pulsar users should upgrade to at least 2.11.4.
3.0 Apache Pulsar users should upgrade to at least 3.0.3.
3.1 Apache Pulsar users should upgrade to at least 3.1.3.
3.2 Apache Pulsar users should upgrade to at least 3.2.1.

Users operating versions prior to those listed above should upgrade to the aforementioned patched versions or newer versions.

References

Published by the National Vulnerability Database Mar 12, 2024
Published to the GitHub Advisory Database Mar 12, 2024
Reviewed Mar 13, 2024
Last updated May 2, 2024

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
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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:C/C:L/I:L/A:N

EPSS score

0.045%
(16th percentile)

Weaknesses

CVE ID

CVE-2024-28098

GHSA ID

GHSA-g627-r579-rw35

Source code

Credits

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