WaratekVRT Sign in

CVE-2021-41571 Apache Pulsar

Affected softwareApache Pulsar
Severity6.5 Medium CVSS 3.1 2 scores
Fixed in2.7.4, 2.8.1
WeaknessIncorrect authorization (CWE-863)
Published1 Feb 2022
Updated17 Jun 2026

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.

CWE-20 · Improper input validation

Exploitation status

No public exploit

No exploit has been reported in the sources we check. Published 4 years ago.

  • CISA KEV not listed
  • VulnCheck KEV not listed
  • CISA Vulnrichment no assessment published
  • Indexed PoC none indexed
  • EPSS 1.7% chance in 30 days

Waratek protection

No exploit published

Within Waratek scope. In the sources we check, nobody has published exploit code for this CVE or reported it being exploited.

A public code fix exists: apache/pulsar #11852.

  • Protection none
  • Action unverified
  • Review automated Upstream data
  • Record active
Decided by Medium or Low severity, no CISA or VulnCheck KEV listing, no PoC clearing the evidence bar, no CISA verdict, no Oracle advisory
Finding This CVE is MEDIUM severity, is not listed in CISA KEV or VulnCheck KEV, has no public exploit or PoC in any indexed source, carries no CISA Vulnrichment finding of a demonstrated exploit, and is not part of an Oracle Critical Patch Update. None of the signals that would put it in front of an engineer is present, and the volume of CVEs below that bar is too great to take one at a time, so no rule is written for it. This is a decision about what we act on, not a finding that the CVE is harmless — a patch may well be derivable, and a low-severity defect can still be one link in a longer chain.

CVSS

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

We show the highest score from the newest CVSS version. Scores from different versions can't be compared, and the first score listed is sometimes a 0.0 placeholder.

VersionScoreBandVectorAssignerType
CVSS 3.1 6.5 MEDIUM CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N NVD Primary published
CVSS 2.0 4.0 none AV:N/AC:L/Au:S/C:P/I:N/A:N NVD Primary

Affected software and releases

Maven packages

Affected and fixed versions, from OSV.dev
PackageIntroducedFixedLast affected
org.apache.pulsar:pulsar 0 none 2.6.4
org.apache.pulsar:pulsar 2.7.0 2.7.4 unbounded
org.apache.pulsar:pulsar 2.8.0 2.8.1 unbounded

Products and versions

2 products, 6 version entries
SourceVendorProductSchemeAffected versions
nvd apache pulsar generic ≥ 2.6.0 and < 2.6.4 · ≥ 2.7.0 and < 2.7.3 · 2.8.0
osv org.apache.pulsar pulsar generic ≤ 2.6.4 · ≥ 2.7.0 and < 2.7.4 · ≥ 2.8.0 and < 2.8.1

References

URLTags
https://github.com/apache/pulsar/issues/11814 WEB
https://github.com/apache/pulsar/pull/11852 WEB
https://github.com/apache/pulsar/pull/11912 WEB
https://github.com/apache/pulsar/pull/11913 WEB
https://github.com/apache/pulsar PACKAGE
https://github.com/apache/pulsar/releases/tag/v2.7.4 WEB
https://github.com/apache/pulsar/releases/tag/v2.8.1 WEB
https://lists.apache.org/thread/8n3k7pvyh4cf9q2jfzb6pb32ync6xlvr WEB
https://pulsar.apache.org/admin-rest-api/#operation/getLastMessageId WEB

Timeline

Published2022-02-01By the CVE Program.
NVD record modified2026-06-17NVD's own last-modified date for this record.