CVE-2019-19085
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 · uneditedA persistent cross-site scripting (XSS) vulnerability in Octopus Server 3.4.0 through 2019.10.5 allows remote authenticated attackers to inject arbitrary web script or HTML.
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 · high confidenceA stored/persistent cross-site scripting (XSS) vulnerability exists in Octopus Server versions 3.4.0 through 2019.10.5, allowing authenticated remote attackers to inject malicious JavaScript or HTML into the web application. The malicious payload persists and executes when other users view the affected content, enabling session hijacking, defacement, or phishing attacks.
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>= 3.4.0, <= 2019.10.5CVSS 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.
-
Verify Octopus Server is installedCheck for Octopus Server processes running on the host, or look for the Octopus Web Portal accessible via browser at the configured server URL (default port 80/443).Affected if Octopus Server is found running or accessible on the network.
-
Determine installed Octopus Server versionLog in to the Octopus Web Portal as an administrator. Navigate to the Configuration > About page, or run 'octopus.server --version' from the command line on the server host if the CLI is available.Affected if The displayed version falls within the range 3.4.0 through 2019.10.5.
-
Confirm authentication is enabledVerify that Octopus Server requires user authentication. Check if the login page is present and that unaxenticated access to sensitive areas is restricted.Affected if Authentication is required for access, meaning an attacker would need valid credentials to exploit the XSS flaw.
-
Identify user-supplied content fieldsIn the Octopus Web Portal, identify areas where authenticated users can input custom content, such as project descriptions, variable values, release notes, or team names.Affected if User-editable text fields exist in the application, which are the potential injection points for the stored XSS.
You are affected if Octopus Server is running with a version between 3.4.0 and 2019.10.5 inclusive and authenticated users can input custom content into the application.
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 Octopus Server to version 2019.10.6 or later. If immediate patching is not possible, implement input validation and output encoding on all user-supplied content fields, and consider deploying Content Security Policy (CSP) headers to mitigate XSS execution.
- Consultation4.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-19085 — 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-2019-19085 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