First published: Tue Feb 01 2022(Updated: )
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.
Credit: security@apache.org security@apache.org security@apache.org
Affected Software | Affected Version | How to fix |
---|---|---|
Apache Pulsar | >=2.6.0<2.6.4 | |
Apache Pulsar | >=2.7.0<2.7.3 | |
Apache Pulsar | =2.8.0 | |
maven/org.apache.pulsar:pulsar | =2.8.0 | 2.8.1 |
maven/org.apache.pulsar:pulsar | >=2.7.0<=2.7.3 | 2.7.4 |
maven/org.apache.pulsar:pulsar | <=2.6.4 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2021-41571 is a vulnerability in Apache Pulsar that allows unauthorized access to data from BookKeeper.
CVE-2021-41571 allows an authenticated user to access data from BookKeeper that does not belong to the topics they have access to by using the Admin API get-message-by-id function.
CVE-2021-41571 has a severity score of 6.5 (medium).
CVE-2021-41571 affects Apache Pulsar versions 2.6.0 to 2.6.4, 2.7.0 to 2.7.3, and 2.8.0.
To fix CVE-2021-41571 in Apache Pulsar, upgrade to version 2.7.4 or 2.8.1.