CVE-2020-24618
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 versions before 2020.3.4313, 2020.2.11008, 2020.1.11011, 2019.1.65514, 2019.2.65515, and 2019.3.65516, an attacker can retrieve an issue description without appropriate access.
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 before 2020.3.4313, 2020.2.11008, 2020.1.11011, 2019.1.65514, 2019.2.65515, and 2019.3.65516 contain an Insecure Direct Object Reference (IDOR) vulnerability where attackers can bypass access controls to retrieve issue descriptions they are not authorized to view. This is a broken access control issue in the issue retrieval API.
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< 2019.1.65514>= 2019.2.0, < 2019.2.65515>= 2019.3, < 2019.3.65516>= 2020.1, < 2020.1.11011>= 2020.2, < 2020.2.11008>= 2020.3, < 2020.3.4313CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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 version numberAccess YouTrack admin dashboard and navigate to About section, or check the version.txt file in the YouTrack installation directory, or view the version displayed on the login page footerAffected if Version number falls below 2019.1.65514; or is 2019.2.x below 2019.2.65515; or is 2019.3.x below 2019.3.65516; or is 2020.1.x below 2020.1.11011; or is 2020.2.x below 2020.2.11008; or is 2020.3.x below 2020.3.4313
-
Verify issue retrieval API accessibilityConfirm that the YouTrack REST API endpoint for issue retrieval (typically /api/issues/{issueId}) is exposed and accessible to usersAffected if The API endpoint is accessible without additional authorization checks beyond basic authentication
-
Confirm user role configurationReview YouTrack user roles and permissions to determine if users can access issues outside their authorized projectsAffected if Users with limited project access can query and retrieve issue descriptions from projects they should not have access to via direct API requests
You are affected if your YouTrack version is within any of the vulnerable version ranges and the issue retrieval API is accessible to users who should not have full visibility to all issues.
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 data2019.1.655142019.2.655152019.3.65516
Upgrade YouTrack to version 2020.3.4313 or later (or the appropriate patched version for the branch in use).
- Consultation2.0 h
- Implementation4.0 h
- Testing4.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,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-24618 — 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-24618 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