YoutrackApplication · Jetbrains

CVE-2020-27625

MEDIUM · 5.3 CVSS v3.1 Published 2020-11-16
Fix available
A fix is available. Upgrade to 2020.3.888 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
In JetBrains YouTrack before 2020.3.888, notifications might have mentioned inaccessible issues.

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 confidence

In YouTrack versions prior to 2020.3.888, the notification system could include references to issues that users were not permitted to access, potentially exposing sensitive information such as issue IDs or titles to unauthorized users through email or in-app notifications.

MitigationUpgrade YouTrack to version 2020.3.888 or later to ensure notification logic properly checks user permissions before referencing issues.

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
YoutrackApplication
Affected:< 2020.3.888

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check YouTrack version
    Access the YouTrack administration interface and navigate to About (typically at /admin/system) or check the build number in the footer of any YouTrack page
    Affected if Version is earlier than 2020.3.888 (for example, 2020.3.887, 2020.2.x, etc.)
  2. Verify email notifications are configured
    Navigate to Administration > Notifications > Email Settings and check if outgoing email server is configured and enabled
    Affected if Email notifications are enabled and the YouTrack version is vulnerable
  3. Confirm user permission restrictions exist
    Review user groups and project memberships in Administration > Users and Groups. Identify users who have restricted access to certain projects or issues
    Affected if There are users with limited access to specific issues or projects in the system
  4. Check notification rules
    Navigate to Administration > Notifications > Notification Rules and review which rules are active, particularly those that might send notifications to users about issues they may not have full access to
    Affected if Notification rules are configured to alert users about issues in projects where they have limited permissions

Your environment is affected if YouTrack version is earlier than 2020.3.888 AND you have email or in-app notifications enabled with users who have restricted issue access.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 2020.3.888 or later
Fixed in 2020.3.888
Interim mitigation

Upgrade YouTrack to version 2020.3.888 or later to ensure notification logic properly checks user permissions before referencing issues.

Fix this in Youtrack Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-27625 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-27625 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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