CVE-2020-9299
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 · uneditedThere were XSS vulnerabilities discovered and reported in the Dispatch application, affecting name and description parameters of Incident Priority, Incident Type, Tag Type, and Incident Filter. This vulnerability can 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 confidenceCross-site scripting (XSS) vulnerabilities in the Dispatch application allow authenticated users to inject malicious scripts through name and description parameters of Incident Priority, Incident Type, Tag Type, and Incident Filter components. User-supplied input in these fields is rendered without proper sanitization or encoding.
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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 Netflix Dispatch is installedLook for the Dispatch application in your environment, typically deployed as a Python/web application. Check for 'dispatch' in application directories, containers, or service listings.Affected if Netflix Dispatch is present in the environment
-
Check Dispatch version against affected rangeLocate the version file or package metadata (e.g., setup.py, requirements.txt, version.py, or the running application's version endpoint). Compare the installed version to 20201106.Affected if The installed version is earlier than 20201106 (e.g., 20201015, 20200901)
-
Verify authenticated user access to vulnerable componentsLog in as an authenticated user and navigate to the Incident Priority, Incident Type, Tag Type, and Incident Filter configuration areas within the Dispatch admin or settings interface.Affected if Authenticated users can access and modify these component settings
-
Inspect name and description field handlingAs an authenticated user, create or edit an Incident Priority, Incident Type, Tag Type, or Incident Filter. Examine the application's response when submitting HTML or script tags in the name or description fields.Affected if User-supplied name/description fields accept and render unsanitized input containing HTML or script tags
-
Check for existing XSS indicatorsReview application logs or UI output for any stored XSS payloads that may have been injected into the affected component fields. Examine the page source when these fields are displayed.Affected if Previously injected script content appears unescaped in the UI or page source
A user is affected if Netflix Dispatch is installed with a version earlier than 20201106 AND authenticated users can access and modify Incident Priority, Incident Type, Tag Type, or Incident Filter components where name/description fields render without sanitization.
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
Implement context-aware output encoding for all user-supplied name and description fields when rendered in the UI, combined with input validation to reject or sanitize potentially malicious characters and script tags.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-9299 — 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-9299 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