CVE-2021-41571
published 2022-02-01CVE-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. The Admin API…
PriorityP338medium6.5CVSS 3.1
AVNACLPRLUINSUCHINAN
EPSS
1.99%
78.4th percentile
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.
Affected
4 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| apache | pulsar | — | — |
| apache | pulsar | >= 2.6.0 < 2.6.4 | 2.6.4 |
| apache | pulsar | >= 2.7.0 < 2.7.3 | 2.7.3 |
| apache_software_foundation | apache_pulsar | Apache Pulsar – 2.8.0 | — |
CVSS provenance
nvdv3.16.5MEDIUMCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
nvdv2.04.0MEDIUMAV:N/AC:L/Au:S/C:P/I:N/A:N
vendor_redhat6.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
OSV
Improper Input Validation in Apache Pulsar
osv·2022-02-02
CVE-2021-41571 [MEDIUM] Improper Input Validation in Apache Pulsar
Improper Input Validation in Apache Pulsar
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.
GHSA
Improper Input Validation in Apache Pulsar
ghsa·2022-02-02
CVE-2021-41571 [MEDIUM] CWE-20 Improper Input Validation in Apache Pulsar
Improper Input Validation in Apache Pulsar
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.
Red Hat
pulsar: Pulsar Admin API allows access to data from other tenants using getMessageById API
vendor_redhat·2022-01-31·CVSS 6.5
CVE-2021-41571 [MEDIUM] CWE-863 pulsar: Pulsar Admin API allows access to data from other tenants using getMessageById API
pulsar: Pulsar Admin API allows access to data from other tenants using getMessageById API
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 Pu
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
https://github.com/apache/pulsar/issues/11814https://lists.apache.org/thread/8n3k7pvyh4cf9q2jfzb6pb32ync6xlvrhttps://pulsar.apache.org/admin-rest-api/#operation/getLastMessageIdhttps://github.com/apache/pulsar/issues/11814https://lists.apache.org/thread/8n3k7pvyh4cf9q2jfzb6pb32ync6xlvrhttps://pulsar.apache.org/admin-rest-api/#operation/getLastMessageId
2022-02-01
Published