Skip to content

Improper Input Validation in Apache Pulsar

Moderate severity GitHub Reviewed Published Feb 2, 2022 to the GitHub Advisory Database • Updated Jul 19, 2023

Package

maven org.apache.pulsar:pulsar (Maven)

Affected versions

<= 2.6.4
>= 2.7.0, <= 2.7.3
= 2.8.0

Patched versions

2.7.4
2.8.1

Description

In Apache Pulsar it is possible to access data from BookKeeper that does not belong to the topics accessible by the authenticated user. The Admin API get-message-by-id requires the user to input a topic and a ledger id. The ledger id is a pointer to the data, and it is supposed to be a valid it for the topic. Authorisation controls are performed against the topic name and there is not proper validation the that ledger id is valid in the context of such ledger. So it may happen that the user is able to read from a ledger that contains data owned by another tenant. This issue affects Apache Pulsar Apache Pulsar version 2.8.0 and prior versions; Apache Pulsar version 2.7.3 and prior versions; Apache Pulsar version 2.6.4 and prior versions.

References

Published by the National Vulnerability Database Feb 1, 2022
Published to the GitHub Advisory Database Feb 2, 2022
Reviewed Feb 3, 2022
Last updated Jul 19, 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
High
Integrity
None
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:U/C:H/I:N/A:N

EPSS score

0.087%
(39th percentile)

Weaknesses

CVE ID

CVE-2021-41571

GHSA ID

GHSA-3whx-qrj5-hh2h

Source code

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