dbcve.org
Git ChangelogApplication · Jenkins

CVE-2019-10414

MEDIUM · 6.5 CVSS v3.1 Published 2019-09-25
Fix available
A fix is available. Upgrade to after 2.17 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
Jenkins Git Changelog Plugin 2.17 and earlier stored credentials unencrypted in job config.xml files on the Jenkins master where they could be viewed by users with Extended Read permission, or 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 confidence

The Jenkins Git Changelog Plugin versions 2.17 and earlier stored credentials unencrypted within job config.xml files on the Jenkins master. Users with Extended Read permission or filesystem access to the Jenkins master could view these plaintext credentials.

MitigationUpdate the Git Changelog Plugin to a version newer than 2.17, and rotate any credentials that may have been exposed. Review and restrict Extended Read permissions as part of remediation.

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
Git ChangelogApplication
Affected:<= 2.17

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

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

  1. Check if Git Changelog Plugin is installed
    Navigate to Jenkins > Manage Jenkins > Manage Plugins > Installed, or use the Jenkins CLI: java -jar jenkins-cli.jar -s http://localhost:8080 list-plugins | grep -i 'git-changelog'
    Affected if The plugin appears in the list of installed plugins
  2. Identify the installed version of Git Changelog Plugin
    In Jenkins > Manage Jenkins > Manage Plugins > Installed, find the Git Changelog plugin and note the version number displayed
    Affected if The version number is 2.17 or lower (e.g., 2.17, 2.16, 2.15, etc.)
  3. Identify jobs using Git Changelog Plugin
    Search for jobs with Git Changelog configuration: grep -r 'gitChangelog' $JENKINS_HOME/jobs/*/config.xml, or review job configurations in the Jenkins UI for Git Changelog build steps
    Affected if One or more jobs contain gitChangelog configuration elements in their config.xml files
  4. Inspect job config.xml files for plaintext credentials
    Examine the config.xml files of jobs using Git Changelog: cat $JENKINS_HOME/jobs/JOBNAME/config.xml | grep -i 'username\|password\|credential', look for plaintext username/password or credentials visible in gitChangelog or related XML elements
    Affected if Credentials appear in plaintext (not encrypted or masked) within the config.xml file
  5. Verify if Extended Read permission is granted broadly
    Review Jenkins authorization matrix: Manage Jenkins > Configure Global Security > Authorization, check if 'Extended Read' permission is given to users or groups beyond administrators
    Affected if Extended Read permission is enabled for non-admin users or anonymous users

You are affected if the Git Changelog Plugin version is 2.17 or earlier AND your Jenkins jobs contain Git Changelog configurations with stored credentials visible in plaintext in config.xml files.

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 a release after 2.17
Interim mitigation

Update the Git Changelog Plugin to a version newer than 2.17, and rotate any credentials that may have been exposed. Review and restrict Extended Read permissions as part of remediation.

Fix this in Git Changelog Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
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,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-10414 — 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-2019-10414 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