Back

MEDIUM

Pulsar Admin API allows access to data from other tenants using getMessageById API

Published Feb 1, 2022

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.

Affected products

Remediation

Vendor solution

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 (14)

Change history (0)

No recorded changes yet.

Sources
CVE.org / MITRE
Status PUBLISHED
Assigner apache
Published Feb 1, 2022
Updated Aug 4, 2024
Reserved Sep 23, 2021
NVD
Status Modified
Modified Jun 17, 2026
Red Hat
Severity Moderate
Public date Jan 31, 2022
ENISA EUVD
Assigner apache
Published Feb 1, 2022
Updated Aug 4, 2024
Exploited since n/a
EUVD-2022-0797 GHSA-3WHX-QRJ5-HH2H