CVE-2020-15820
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 JetBrains YouTrack before 2020.2.6881, the markdown parser could disclose hidden file existence.
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 confidenceThe markdown parser in JetBrains YouTrack versions prior to 2020.2.6881 contains an information disclosure vulnerability that allows attackers to determine the existence of hidden files on the server through specially crafted markdown input.
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.6881CVSS 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.
-
Determine installed YouTrack versionLog into YouTrack as an administrator and navigate to Administration > Overview, or check the version displayed in the YouTrack footer on any page. The version number is typically displayed in the format YYYY.X.build (e.g., 2020.1.5283).Affected if The installed version is a version number less than 2020.2.6881 (e.g., 2020.1.x, 2020.0.x, 2019.x.x, etc.)
-
Verify markdown input is accessibleConfirm that users (or unauthenticated users, depending on configuration) can submit markdown content through YouTrack features such as issue descriptions, comments, or wiki pages. This is default functionality in YouTrack.Affected if Markdown input is accepted (which is the default state in YouTrack) and the version is below 2020.2.6881
-
Check network exposureReview firewall rules, VPN configuration, and YouTrack's authentication settings to determine whether the YouTrack instance is accessible from untrusted networks or the public internet.Affected if YouTrack is accessible from networks where untrusted users can submit markdown content
You are affected if your YouTrack installation version is below 2020.2.6881 and users can submit markdown input to 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 data2020.2.6881
Upgrade YouTrack to version 2020.2.6881 or later to patch the vulnerability. If immediate upgrade is not possible, restrict network access to YouTrack instances as a temporary compensating control.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-15820 — 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-15820 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