CVE-2021-41571
In Apache Pulsar it is possible to access data from BookKeeper that does not belong to the topics accessible by the authenticated user.
Does this matter?
Lower severity and a low EPSS score (1.73%). Track it; it rarely justifies an emergency change on its own.
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.
- CVSS 3.1
- 6.5 MEDIUMCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
- EPSS
- 1.73% probability · 76th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-863
- Affected
- apache/pulsar
- Source
- security@apache.org
References
- https://github.com/apache/pulsar/issues/11814Exploit, Issue Tracking, Patch, Third Party Advisory
- https://lists.apache.org/thread/8n3k7pvyh4cf9q2jfzb6pb32ync6xlvrMailing List, Vendor Advisory
- https://pulsar.apache.org/admin-rest-api/#operation/getLastMessageIdPatch, Vendor Advisory
- https://github.com/apache/pulsar/issues/11814Exploit, Issue Tracking, Patch, Third Party Advisory
- https://lists.apache.org/thread/8n3k7pvyh4cf9q2jfzb6pb32ync6xlvrMailing List, Vendor Advisory
- https://pulsar.apache.org/admin-rest-api/#operation/getLastMessageIdPatch, Vendor Advisory
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.