CVE-2020-15819
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.10643 was vulnerable to SSRF that allowed scanning internal ports.
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 confidenceJetBrains YouTrack versions prior to 2020.2.10643 contained a Server-Side Request Forgery (SSRF) vulnerability that allowed authenticated or unauthenticated attackers to induce the server to make HTTP requests to arbitrary ports on internal network resources, enabling internal port scanning and service enumeration.
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.10643CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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.
-
Locate YouTrack installationIdentify the server where YouTrack is installed and find its installation directory, typically in /opt/youtrack, /home/youtrack, or a custom directory defined during installation.Affected if YouTrack software is found on the system
-
Determine installed YouTrack versionAccess the YouTrack web interface and check the version number typically displayed in the footer or under Administration > System > Overview. Alternatively, check the conf/youtrack.properties file in the installation directory for the version property.Affected if Unable to retrieve version information or version displays as a pre-2020.2 release
-
Compare version against vulnerable rangeVerify the installed version against the affected range: versions prior to 2020.2.10643 are vulnerable. The full version string should be examined (for example, 2020.1.x, 2020.2.0 through 2020.2.10642).Affected if Installed version is lower than 2020.2.10643 (for example, 2020.2.10000 or 2020.1.5)
-
Assess network exposureDetermine if the YouTrack server is directly accessible from the internet or untrusted networks, as the SSRF can be exploited by unauthenticated attackers.Affected if Server is exposed to untrusted networks without firewall restrictions
You are affected if YouTrack is running version 2020.2.10642 or any earlier version (such as 2020.2.x before 10643 or 2020.1.x), especially if the server is network-accessible to untrusted users.
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.10643
Upgrade YouTrack to version 2020.2.10643 or later. If immediate upgrade is not feasible, restrict network access to the YouTrack server and monitor outbound connections for suspicious internal targeting.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.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 $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-15819 — 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-15819 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