CVE-2021-41571

Medium

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.

SeverityMedium
CVSS6.5
Exploit probability—
ProductApache Pulsar
PublishedFeb 1, 2022
First seenFeb 1, 2022

How to fix

Update
  • apache pulsar2.6.4, 2.7.3 or later
  • org.apache.pulsar:pulsar2.7.4, 2.8.1 or later

Affected products

ProductAffected versionsFixed in
apache pulsar2.6.0 ≤ v < 2.6.4, 2.7.0 ≤ v < 2.7.3, 2.8.02.6.4, 2.7.3
org.apache.pulsar:pulsarMavenv ≤ 2.6.4, 2.7.0 ≤ v < 2.7.4, 2.8.0 ≤ v < 2.8.12.7.4, 2.8.1

Check your version

Choose the product and enter the version you run to see whether it falls in the affected range.

In the Intelligence 360 plan

Attack Surface Management

See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.