dbcve.org
YoutrackApplication · Jetbrains

CVE-2021-25767

MEDIUM · 5.3 CVSS v3.1 Published 2021-02-03
Fix available
A fix is available. Upgrade to 2020.6.1767 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.6.1767, an issue's existence could be disclosed via YouTrack command execution.

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 confidence

In JetBrains YouTrack versions prior to 2020.6.1767, the command execution feature allowed attackers to determine whether specific issues existed in the system, potentially revealing sensitive project information through crafted command inputs.

MitigationUpgrade YouTrack to version 2020.6.1767 or later to remediate this vulnerability.

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.6.1767

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. Verify YouTrack installation exists
    Check for YouTrack installation directories or services running YouTrack. Common locations include /opt/youtrack, /usr/share/youtrack, or the YouTrack service process.
    Affected if YouTrack software is present in the environment
  2. Determine installed YouTrack version
    Access the YouTrack administration interface and navigate to About or Version settings, or check the youtrack.jar/version file in the installation directory.
    Affected if A version number is returned that can be compared
  3. Compare version against vulnerability threshold
    Compare the installed version number to 2020.6.1767 using semantic versioning. Any version less than 2020.6.1767 is in the affected range.
    Affected if Installed version is 2020.6.x less than 1767, or any version prior to 2020.6.x (e.g., 2020.5, 2020.4, etc.)
  4. Confirm command execution feature is accessible
    Verify the YouTrack command execution feature is enabled and accessible to users. This feature is typically available in issue views where users can enter commands.
    Affected if The command execution feature is enabled and accessible to users in the YouTrack instance

The environment is affected if YouTrack is installed with a version lower than 2020.6.1767 and the command execution feature is enabled.

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.6.1767 or later
Fixed in 2020.6.1767
Interim mitigation

Upgrade YouTrack to version 2020.6.1767 or later to remediate this vulnerability.

Fix this in Youtrack Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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

Check whether your project pulls in CVE-2021-25767 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2021-25767 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