CVE-2020-15822
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.10514, SSRF is possible because URL filtering can be escaped.
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 confidenceIn JetBrains YouTrack before version 2020.2.10514, an SSRF vulnerability exists due to URL filtering that can be escaped/bypassed, allowing attackers to make the server perform requests to unintended internal or external resources.
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.10514CVSS 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
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
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.
-
Check installed YouTrack versionNavigate to the YouTrack administration interface and go to About (typically at /admin/about) or check the version file in the YouTrack installation directory. You can also use the command: grep -r 'buildNumber' <youtrack_installation_directory>/conf or check the startup logs.Affected if The installed version is lower than 2020.2.10514 (e.g., 2020.2.x before .10514, or any earlier version).
-
Verify URL request handling is exposedIdentify any YouTrack features that accept user-supplied URLs, such as the issue linkers, webhooks, or integrations that make outbound HTTP requests. Check if the YouTrack server can directly accept URL inputs from users in fields like 'Link', 'Attachment', or custom fields.Affected if The YouTrack instance has any plugins, integrations, or features enabled that allow users to submit or configure outbound URLs (webhooks, external issue links, service URLs).
-
Review YouTrack access logs for suspicious outbound requestsExamine YouTrack server access logs and proxy logs for unusual outbound HTTP/HTTPS requests, particularly to internal network addresses (10.x.x.x, 192.168.x.x, 127.x.x.x, 172.16-31.x.x), cloud metadata endpoints (169.254.169.254), or unusual external domains. Logs are typically in <youtrack_installation_directory>/logs/ or can be exported from the admin interface.Affected if Logs contain requests to internal IPs, localhost, cloud metadata services, or unexpected internal resources that were not initiated by legitimate administrators.
-
Monitor network connections from YouTrack serverUse netstat, ss, or firewall logs on the YouTrack server host to observe outbound network connections. Look for connections to ports or IPs that were not explicitly configured by administrators.Affected if There are unexpected established outbound connections to internal addresses or unusual external destinations that do not correspond to configured integrations.
A YouTrack installation is affected if its version is below 2020.2.10514 AND it has features or integrations that allow user-supplied URLs to trigger outbound HTTP requests.
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.10514
Upgrade YouTrack to version 2020.2.10514 or later. If immediate upgrade is not possible, restrict outgoing network connections from the YouTrack server and monitor for suspicious requests.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-15822 — 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-15822 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