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 id for the topic. Authorisation controls are performed against the topic name and there is not proper validation that the 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. This issue is being tracked as https://github.com/apache/pulsar/issues/11814 Mitigation: If you are running Pulsar behind a proxy you can disable access to the REST API for the flawed API /admin/v2/non-persistent/{tenant}/{namespace}/{topic}/ledger/{ledgerId}/entry/{entryId} References: https://pulsar.apache.org/admin-rest-api/#operation/getLastMessageId https://github.com/apache/pulsar/issues/11814
Marking services-managed-kafka affected/delegated. Affected code present: services-managed-kafka/mk-ci-cd/kas-fleetshard-operator:b165510/org.apache.pulsar:pulsar-client-all-2.6.0 https://gitlab.cee.redhat.com/mk-ci-cd/kas-fleetshard/blob/production/pom.xml services-managed-kafka/mk-ci-cd/kas-fleetshard-sync:b165510/org.apache.pulsar:pulsar-client-all-2.6.0 https://gitlab.cee.redhat.com/mk-ci-cd/kas-fleetshard/blob/production/pom.xml