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
Link | Resource |
---|---|
https://github.com/apache/pulsar/issues/11814 | Exploit Issue Tracking Patch Third Party Advisory |
https://lists.apache.org/thread/8n3k7pvyh4cf9q2jfzb6pb32ync6xlvr | Mailing List Vendor Advisory |
https://pulsar.apache.org/admin-rest-api/#operation/getLastMessageId | Patch Vendor Advisory |
History
No history.
MITRE Information
Status: PUBLISHED
Assigner: apache
Published: 2022-02-01T12:40:53
Updated: 2023-07-18T11:52:20.375Z
Reserved: 2021-09-23T00:00:00
Link: CVE-2021-41571
JSON object: View
NVD Information
Status : Analyzed
Published: 2022-02-01T13:15:09.663
Modified: 2023-07-24T13:52:24.607
Link: CVE-2021-41571
JSON object: View
Redhat Information
No data.
CWE