CVE-2019-19376
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 Octopus Deploy before 2019.10.6, an authenticated user with TeamEdit permission could send a malformed Team API request that bypasses input validation and causes an application level denial of service condition. (The fix for this was also backported to LTS 2019.9.8 and LTS 2019.6.14.)
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 confidenceAn authenticated user with TeamEdit permission in Octopus Deploy can send a malformed Team API request that bypasses input validation, triggering an application-level denial of service. This affects versions prior to 2019.10.6 (and LTS versions prior to 2019.9.8 and 2019.6.14).
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< 2019.10.7>= 2019.6.0, < 2019.6.14>= 2019.9.0, < 2019.9.8CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
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 installed Octopus Deploy versionNavigate to the Octopus Web UI, click on the user profile icon in the top right, and view the version number displayed, or run 'octo version' from the server command line if availableAffected if The version is earlier than 2019.10.7, or falls between 2019.6.0-2019.6.13, or falls between 2019.9.0-2019.9.7
-
Verify TeamEdit permission existsIn the Octopus Deploy web interface, go to Configuration -> Users -> [select a user] -> Roles, or go to Configuration -> Teams -> [select a team] -> Roles, and check if any role assignment includes TeamEditAffected if Any user account or service account is assigned the TeamEdit permission
-
Review API request logs for Team endpointsIn the Octopus web interface, go to Configuration -> Audit to view recent activity, filter for 'Team' related API calls, or check server logs for requests to /api/teams endpoints that returned 500 errors or caused timeoutsAffected if Malformed Team API requests are present in logs, or there are records of 500 errors on Team endpoints
-
Check for DoS symptoms on Team operationsIn the Octopus web interface, attempt to access the Teams configuration page (Configuration -> Teams), or monitor server response times when Team-related operations are performedAffected if The Teams page loads slowly, times out, or returns errors indicating a denial of service condition
The environment is affected if the installed Octopus Deploy version falls within 2019.6.0-2019.6.13, 2019.9.0-2019.9.7, or earlier than 2019.10.7 AND any user has TeamEdit permission enabled.
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 data2019.6.142019.9.82019.10.7
Upgrade Octopus Deploy to version 2019.10.6 or later (or patched LTS versions 2019.9.8/2019.6.14), and review and restrict TeamEdit permission assignments to only necessary personnel.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-19376 — 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-19376 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