Incorrect Authorization vulnerability in Apache Software Foundation Apache Pulsar. This issue affects Apache Pulsar: before 2.10.4, and 2.11.0. When a client connects to the Pulsar Function Worker via the Pulsar Proxy where the Pulsar Proxy uses mTLS authentication to authenticat...
Product
org.apache.pulsar/pulsar vulnerabilities
4 published CVES affecting org.apache.pulsar/pulsar, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 4
- Critical
- 1
- High
- 1
- Medium
- 2
- Low
- 0
- Unscored
- 0
- CISA KEV
- 0
Latest org.apache.pulsar/pulsar CVEs
Newest publication first
-
HighCVSS 8.8 EPSS 1.0%
-
MediumCVSS 6.5 EPSS 1.5% PoC
Improper Input Validation vulnerability in Proxy component of Apache Pulsar allows an attacker to make TCP/IP connection attempts that originate from the Pulsar Proxy's IP address. When the Apache Pulsar Proxy component is used, it is possible to attempt to open TCP/IP connection...
-
CVE-2021-41571 Pulsar Admin API allows access to data from other tenants using getMessageById API
PublishedMediumCVSS 6.5 EPSS 1.7%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 t...
-
CriticalCVSS 9.8 EPSS 52.9%
If Apache Pulsar is configured to authenticate clients using tokens based on JSON Web Tokens (JWT), the signature of the token is not validated if the algorithm of the presented token is set to "none". This allows an attacker to connect to Pulsar instances as any user (incl. admi...
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.