CVE-2021-41571

Source
https://nvd.nist.gov/vuln/detail/CVE-2021-41571
Import Source
https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2021-41571.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2021-41571
Aliases
Published
2022-02-01T13:15:09Z
Modified
2024-06-06T13:44:38.059289Z
Severity
  • 6.5 (Medium) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N CVSS Calculator
Summary
[none]
Details

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

Affected packages

Git / github.com/apache/pulsar

Affected ranges

Type
GIT
Repo
https://github.com/apache/pulsar
Events

Affected versions

v2.*

v2.6.0
v2.6.0-candidate-1
v2.6.1
v2.6.1-candidate-1
v2.6.2
v2.6.2-candidate-1
v2.6.2-candidate-2
v2.6.3
v2.6.3-candidate-1
v2.6.3-candidate-2