CVE-2019-12866
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 · uneditedAn Insecure Direct Object Reference, with Authorization Bypass through a User-Controlled Key, was possible in JetBrains YouTrack. The issue was fixed in 2018.4.49168.
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 confidenceAn Insecure Direct Object Reference (IDOR) vulnerability combined with Authorization Bypass through User-Controlled Key in JetBrains YouTrack allowed attackers to manipulate object references to access unauthorized data or functionality without proper authentication checks.
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< 2018.4.49168CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
-
Confirm JetBrains YouTrack installationIdentify whether JetBrains YouTrack is deployed in your environmentAffected if YouTrack is present and accessible
-
Locate YouTrack version informationFind the installed YouTrack version number (typically accessible through the administration panel, product UI, or installation files)Affected if Version number cannot be located or confirmed
-
Compare version against vulnerable rangeCheck if the installed version is earlier than 2018.4.49168Affected if Installed version is less than 2018.4.49168
Your environment is affected if JetBrains YouTrack is installed and the version is earlier than 2018.4.49168
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.
dbcve · scoped2018.4.49168
Upgrade JetBrains YouTrack to version 2018.4.49168 or later to patch the IDOR vulnerability.
YouTrack 2018.4.49168 or later
- 1. Backup your YouTrack database and configuration files before proceeding with any upgrade.
- 2. Download the fixed version of YouTrack (2018.4.49168 or later) from the official JetBrains download page.
- 3. Follow the standard YouTrack upgrade procedure: stop the YouTrack service, replace the installation files, and start the service again.
- 4. Review the upgrade notes in JetBrains documentation for any additional migration steps required for your specific version jump.
- 5. Verify that YouTrack starts successfully and that user authentication and authorization are functioning correctly.
- 6. Test that the IDOR vulnerability is no longer exploitable by attempting to access resources via manipulated object references (if you have security testing capabilities).
Generated from the published advisory — verify against the referenced sources before acting.
- 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-2019-12866 — 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-2019-12866 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