PT-2026-120760 · Apache · Apache Pulsar Manager
CVSS v4.0
10
Critical
| Vector | AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
Name of the Vulnerable Software and Affected Versions
Apache Pulsar Manager versions 0.1.0 through 0.4.0
Description
Apache Pulsar Manager contains several security flaws. The process for creating the initial administrator account is accessible without authentication and remains available after initialization, allowing any network-reachable user to create an administrator account. In versions 0.3.0 and later, the software does not distinguish between privilege levels, granting all accounts full administrative rights. Additionally, requests proxied to the Pulsar admin API bypass authentication, enabling unauthenticated users to perform administrative operations using the configured credentials. Furthermore, a requester can specify the destination of a proxied request, causing Pulsar Manager to send its configured admin credentials to an arbitrary host. If configured with a token signing key, a Pulsar Manager administrator can generate tokens for the cluster.
Recommendations
Stop using Apache Pulsar Manager and remove all existing deployments.
Replace any Pulsar credentials or token signing keys that were used in Pulsar Manager configurations.
Restrict network access to trusted administrators and do not expose the software to untrusted networks until it is removed.
Fix
Missing Authentication
Found an issue in the description? Have something to add? Feel free to write us 👾
Weakness Enumeration
Related Identifiers
Affected Products
Apache Pulsar Manager