GitHub Advisoryadvisory · Maven

GHSA-3whx-qrj5-hh2h Improper Input Validation in Apache Pulsar

MEDIUM Published 2022-02-02 Modified 2022-02-11 Official page ↗
Aliases
CVE-2021-41571
Ecosystem
Maven
Packages
org.apache.pulsar:pulsar
Severity
Moderate
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Weaknesses
CWE-20, CWE-863
Reviewed
2022-02-03

Affected packages

• Maven org.apache.pulsar:pulsar: <= 2.6.4 (no fix yet) • Maven org.apache.pulsar:pulsar: >= 2.7.0, < 2.7.4 → fixed in 2.7.4 • Maven org.apache.pulsar:pulsar: >= 2.8.0, < 2.8.1 → fixed in 2.8.1

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.

Related

Alias · CVE (1)

  • CVE-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. vulnerability

Weakness · CWE (2)

  • CWE-20 Improper Input Validation weakness
  • CWE-863 Incorrect Authorization weakness

References