Pulsar ManagerApplication · Apache
CVE-2020-17520
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn the Pulsar manager 0.1.0 version, malicious users will be able to bypass pulsar-manager's admin, permission verification mechanism by constructing special URLs, thereby accessing any HTTP API.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceIn Pulsar Manager 0.1.0, a URL construction vulnerability allows malicious users to bypass admin permission verification by crafting special URLs, enabling unauthorized access to any HTTP API within the manager.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Pulsar ManagerApplication
= 0.1.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if Pulsar Manager is installedCheck for running Pulsar Manager processes, Docker containers, or installation directories. Look for the pulsar-manager service, Docker container named 'pulsar-manager', or installation under /opt or /usr/local.Affected if Pulsar Manager software is present in the environment
-
Determine the installed versionCheck the version of the installed Pulsar Manager. This may be visible in the UI footer, returned by the /admin/v2/version endpoint, in Docker image tags, or in the installed package metadata (rpm -qi or dpkg -l for pulsar-manager).Affected if The installed version is exactly 0.1.0
-
Verify admin API accessibilityAttempt to access Pulsar Manager admin API endpoints without valid admin credentials or session. The vulnerability allows crafting special URLs to bypass admin permission checks.Affected if The admin API endpoints are reachable over HTTP/HTTPS without proper authorization bypass being blocked
-
Check network exposureDetermine if the Pulsar Manager web interface and API are exposed to the network. Check firewall rules, reverse proxy configurations, and listen addresses in the manager configuration.Affected if The Pulsar Manager admin interface is network-accessible (not localhost-only or behind strict network access controls)
The environment is affected if Apache Pulsar Manager version 0.1.0 is running and its admin API is network-accessible, allowing URL-based authorization bypass attacks.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade or patch Pulsar Manager to a version that fixes the URL-based authorization bypass; if no patch is available, restrict network access to the manager and implement additional upstream access controls.
Fix this in Pulsar Manager
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-17520 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-17520 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data