Logo
-

Byte Open Security

(ByteOS Network)

Log In

Sign Up

ByteOS

Security
Vulnerability Details
Registries
Custom Views
Weaknesses
Attack Patterns
Filters & Tools
Vulnerability Details :

CVE-2021-41571

Summary
Assigner-apache
Assigner Org ID-f0158376-9dc2-43b6-827c-5f631a4d8d09
Published At-01 Feb, 2022 | 12:40
Updated At-04 Aug, 2024 | 03:15
Rejected At-
Credits

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

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.

Vendors
-
Not available
Products
-
Metrics (CVSS)
VersionBase scoreBase severityVector
Weaknesses
Attack Patterns
Solution/Workaround
References
HyperlinkResource Type
EPSS History
Score
Latest Score
-
N/A
No data available for selected date range
Percentile
Latest Percentile
-
N/A
No data available for selected date range
Stakeholder-Specific Vulnerability Categorization (SSVC)
▼Common Vulnerabilities and Exposures (CVE)
cve.org
Assigner:apache
Assigner Org ID:f0158376-9dc2-43b6-827c-5f631a4d8d09
Published At:01 Feb, 2022 | 12:40
Updated At:04 Aug, 2024 | 03:15
Rejected At:
▼CVE Numbering Authority (CNA)
Pulsar Admin API allows access to data from other tenants using getMessageById API

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
Vendor
The Apache Software FoundationApache Software Foundation
Product
Apache Pulsar
Versions
Affected
  • From Apache Pulsar through 2.8.0 (custom)
Problem Types
TypeCWE IDDescription
CWECWE-863CWE-863 Incorrect Authorization
Type: CWE
CWE ID: CWE-863
Description: CWE-863 Incorrect Authorization
Metrics
VersionBase scoreBase severityVector
Metrics Other Info
unknown
other:
moderate
Impacts
CAPEC IDDescription
Solutions
Configurations
Workarounds

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}

Exploits
Credits
Timeline
EventDate
Replaced By
Rejected Reason
References
HyperlinkResource
https://pulsar.apache.org/admin-rest-api/#operation/getLastMessageId
x_refsource_MISC
https://github.com/apache/pulsar/issues/11814
x_refsource_MISC
https://lists.apache.org/thread/8n3k7pvyh4cf9q2jfzb6pb32ync6xlvr
x_refsource_MISC
Hyperlink: https://pulsar.apache.org/admin-rest-api/#operation/getLastMessageId
Resource:
x_refsource_MISC
Hyperlink: https://github.com/apache/pulsar/issues/11814
Resource:
x_refsource_MISC
Hyperlink: https://lists.apache.org/thread/8n3k7pvyh4cf9q2jfzb6pb32ync6xlvr
Resource:
x_refsource_MISC
▼Authorized Data Publishers (ADP)
CVE Program Container
Affected Products
Metrics
VersionBase scoreBase severityVector
Metrics Other Info
Impacts
CAPEC IDDescription
Solutions
Configurations
Workarounds
Exploits
Credits
Timeline
EventDate
Replaced By
Rejected Reason
References
HyperlinkResource
https://pulsar.apache.org/admin-rest-api/#operation/getLastMessageId
x_refsource_MISC
x_transferred
https://github.com/apache/pulsar/issues/11814
x_refsource_MISC
x_transferred
https://lists.apache.org/thread/8n3k7pvyh4cf9q2jfzb6pb32ync6xlvr
x_refsource_MISC
x_transferred
Hyperlink: https://pulsar.apache.org/admin-rest-api/#operation/getLastMessageId
Resource:
x_refsource_MISC
x_transferred
Hyperlink: https://github.com/apache/pulsar/issues/11814
Resource:
x_refsource_MISC
x_transferred
Hyperlink: https://lists.apache.org/thread/8n3k7pvyh4cf9q2jfzb6pb32ync6xlvr
Resource:
x_refsource_MISC
x_transferred
Information is not available yet
▼National Vulnerability Database (NVD)
nvd.nist.gov
Source:security@apache.org
Published At:01 Feb, 2022 | 13:15
Updated At:24 Jul, 2023 | 13:52

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.

CISA Catalog
Date AddedDue DateVulnerability NameRequired Action
N/A
Date Added: N/A
Due Date: N/A
Vulnerability Name: N/A
Required Action: N/A
Metrics
TypeVersionBase scoreBase severityVector
Primary3.16.5MEDIUM
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Primary2.04.0MEDIUM
AV:N/AC:L/Au:S/C:P/I:N/A:N
Type: Primary
Version: 3.1
Base score: 6.5
Base severity: MEDIUM
Vector:
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Type: Primary
Version: 2.0
Base score: 4.0
Base severity: MEDIUM
Vector:
AV:N/AC:L/Au:S/C:P/I:N/A:N
CPE Matches
The Apache Software Foundation
apache
>>pulsar>>Versions from 2.6.0(inclusive) to 2.6.4(exclusive)
cpe:2.3:a:apache:pulsar:*:*:*:*:*:*:*:*
The Apache Software Foundation
apache
>>pulsar>>Versions from 2.7.0(inclusive) to 2.7.3(exclusive)
cpe:2.3:a:apache:pulsar:*:*:*:*:*:*:*:*
The Apache Software Foundation
apache
>>pulsar>>2.8.0
cpe:2.3:a:apache:pulsar:2.8.0:*:*:*:*:*:*:*
Weaknesses
CWE IDTypeSource
CWE-863Primarysecurity@apache.org
CWE-863Secondarynvd@nist.gov
CWE ID: CWE-863
Type: Primary
Source: security@apache.org
CWE ID: CWE-863
Type: Secondary
Source: nvd@nist.gov
Evaluator Description
Evaluator Impact

Evaluator Solution

Vendor Statements
References
HyperlinkSourceResource
https://github.com/apache/pulsar/issues/11814security@apache.org
Exploit
Issue Tracking
Patch
Third Party Advisory
https://lists.apache.org/thread/8n3k7pvyh4cf9q2jfzb6pb32ync6xlvrsecurity@apache.org
Mailing List
Vendor Advisory
https://pulsar.apache.org/admin-rest-api/#operation/getLastMessageIdsecurity@apache.org
Patch
Vendor Advisory
Hyperlink: https://github.com/apache/pulsar/issues/11814
Source: security@apache.org
Resource:
Exploit
Issue Tracking
Patch
Third Party Advisory
Hyperlink: https://lists.apache.org/thread/8n3k7pvyh4cf9q2jfzb6pb32ync6xlvr
Source: security@apache.org
Resource:
Mailing List
Vendor Advisory
Hyperlink: https://pulsar.apache.org/admin-rest-api/#operation/getLastMessageId
Source: security@apache.org
Resource:
Patch
Vendor Advisory

Change History

0
Information is not available yet

Similar CVEs

0Records found
Details not found