CVE-2020-9300
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 · uneditedThe Access Control issues include allowing a regular user to view a restricted incident, user role escalation to admin, users adding themselves as a participant in a restricted incident, and users able to view restricted incidents via the search feature. If your install has followed the secure deployment guidelines the risk of this is lowered, as this may only be exploited by an authenticated user.
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 confidenceCVE-2020-9300 is an access control vulnerability in an incident management application where multiple authorization flaws allow authenticated users to bypass restrictions. These include viewing restricted incidents, escalating user roles to admin privileges, adding themselves as participants to restricted incidents, and accessing restricted data through the search feature.
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< 20201106CVSS 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.
-
Check the installed Dispatch versionLocate the Dispatch installation and identify the version. In Docker deployments, run 'docker images' or check the image tag. In source installations, check the git tag or version file. Compare against the vulnerable version range: versions released before 20201106Affected if The installed version is any release dated before November 6, 2020 (version < 20201106)
-
Confirm Dispatch is accessible over the networkVerify the Dispatch web interface is reachable by accessing the application's URL or checking listening ports (typically port 8000 or configured HTTP port)Affected if The application is network-accessible and exposes the incident management interface to users
-
Verify multi-user authentication is enabledCheck the Dispatch configuration for authentication settings. Look for auth backends in configuration files or environment variables. Confirm that local authentication or an external identity provider is configuredAffected if User authentication is enabled, meaning regular authenticated users exist in the system who could potentially exploit the authorization bypass
-
Inspect role-based access control configurationReview the application's user role definitions and permission settings in the database or configuration. Check whether incident-level access restrictions are defined but may not be properly enforcedAffected if The system uses role-based access control where incidents can have restricted access but authorization checks may be bypassed
A user is affected if they are running Netflix Dispatch version earlier than 20201106 with authenticated user access enabled, as the authorization bypass flaws allow any authenticated user to view restricted incidents, escalate privileges, and access restricted data through search.
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 data20201106
Fix authorization checks throughout the application to enforce proper access control on incident viewing, user role management, participant assignment, and search functionality. Follow secure deployment guidelines to reduce exploitability.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-9300 — 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-9300 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