CVE-2020-15823
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 · uneditedJetBrains YouTrack before 2020.2.8873 is vulnerable to SSRF in the Workflow component.
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 confidenceJetBrains YouTrack versions prior to 2020.2.8873 contain a Server-Side Request Forgery (SSRF) vulnerability in the Workflow component. This allows an attacker to make the YouTrack server perform arbitrary HTTP requests to internal resources or external systems, potentially accessing internal services or bypassing network segmentation.
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< 2020.2.8873CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 YouTrack versionAccess the YouTrack administration interface and navigate to About or Version section, or check the product banner on the main dashboard. The version number is typically displayed as a numeric string like 2020.1.x or 2020.2.x.Affected if The installed version is less than 2020.2.8873 (for example, 2020.2, 2020.1, 2019.x, etc.)
-
Verify Workflow module accessibilityCheck if the Workflow feature is enabled in YouTrack. This can be done in Administration > Workflows, or by attempting to access the workflow editor interface at /workflows/ endpoint.Affected if The Workflow module is installed and accessible to users who can create or edit workflows
-
Confirm network exposure of YouTrack serverReview the network configuration and determine if the YouTrack server is accessible from untrusted networks or if it has access to internal resources that could be targeted via SSRF.Affected if The YouTrack server can initiate outbound HTTP connections and is reachable by users who can trigger workflow execution
-
Audit workflow execution permissionsIn Administration > Users and Groups, review which users or groups have permissions to create, edit, or execute workflows. Check for any custom workflow rules attached to projects.Affected if Users other than administrators can create or modify workflows, or automated workflow triggers are configured on projects
You are affected if your YouTrack version is prior to 2020.2.8873 AND the Workflow feature is enabled and accessible to users who could trigger the SSRF.
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 data2020.2.8873
Upgrade YouTrack to version 2020.2.8873 or later. If immediate patching is not possible, restrict network access to the YouTrack server and monitor for suspicious outbound requests.
- Consultation2.0 h
- Implementation4.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-15823 — 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-15823 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