Youtrack PluginPlugin / extension · Jenkins
CVE-2019-10287
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 · uneditedJenkins youtrack-plugin Plugin 0.7.1 and older stored credentials unencrypted in its global configuration file on the Jenkins master where they could be viewed by users with access to the master file system.
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 confidenceThe Jenkins youtrack-plugin Plugin version 0.7.1 and older stores credentials unencrypted in plaintext within its global configuration file on the Jenkins master node. Users with filesystem access to the Jenkins master can directly read these stored credentials without any additional authentication or privilege escalation.
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
Youtrack PluginPlugin / extension
<= 0.7.1CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Identify if the youtrack-plugin is installedIn Jenkins, go to Manage Jenkins > Manage Plugins > Installed tab and search for 'youtrack'. Alternatively, check the $JENKINS_HOME/plugins directory for a youtrack folder.Affected if The plugin is present in the Jenkins installation.
-
Determine the installed plugin versionClick on the youtrack-plugin entry in the Installed Plugins list to view its version number. Compare this version against the affected range: 0.7.1 and older.Affected if The installed version is 0.7.1 or lower.
-
Locate the plugin configuration fileNavigate to the Jenkins home directory ($JENKINS_HOME) and locate the configuration file for the youtrack-plugin. This is typically found in the Jenkins global configuration or within the plugin's dedicated configuration directory.Affected if A configuration file for the youtrack-plugin exists on the Jenkins master.
-
Inspect credentials storage in the configuration fileOpen the youtrack-plugin configuration file using a text editor or command-line tool. Search for credential fields (such as passwords, API tokens, or usernames) and verify whether they appear in plaintext or are encrypted (look for encrypted strings starting with {AES}, or similar encoding markers).Affected if Credentials are stored in plaintext (readable, unencrypted strings) rather than being encrypted or masked.
A user is affected if the youtrack-plugin version is 0.7.1 or older and plaintext credentials are present in the plugin's configuration file on the Jenkins master filesystem.
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 dataUpgrade the youtrack-plugin to a version newer than 0.7.1 (if available) that encrypts credentials at rest, and rotate any credentials that may have been exposed through this vulnerability.
Fix this in Youtrack Plugin
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10287 — 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-10287 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