CVE-2021-41571 – org.apache.pulsar:pulsar

Package

Manager: maven
Name: org.apache.pulsar:pulsar
Vulnerable Version: >=0 <=2.6.4 || >=2.7.0 <2.7.4 || =2.8.0 || >=2.8.0 <2.8.1

Severity

Level: Medium

CVSS v3.1: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

CVSS v4.0: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

EPSS: 0.00979 pctl0.75875

Details

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.

Metadata

Created: 2022-02-02T00:01:52Z
Modified: 2022-02-11T17:07:14Z
Source: https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2022/02/GHSA-3whx-qrj5-hh2h/GHSA-3whx-qrj5-hh2h.json
CWE IDs: ["CWE-20", "CWE-863"]
Alternative ID: GHSA-3whx-qrj5-hh2h
Finding: F184
Auto approve: 1