Project InheritanceApplication · Jenkins

CVE-2019-10407

MEDIUM · 6.5 CVSS v3.1 Published 2019-09-25
Fix available
A fix is available. Upgrade to after 2.0.0 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 Project Inheritance Plugin 2.0.0 and earlier displayed a list of environment variables passed to a build without masking sensitive variables contributed by the Mask Passwords Plugin.

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 Project Inheritance Plugin versions 2.0.0 and earlier failed to respect the password masking functionality provided by the Mask Passwords Plugin. When displaying environment variables passed to a build, sensitive variables (passwords, credentials, secrets) were shown in plain text instead of being masked, leading to information disclosure of sensitive authentication data.

MitigationUpgrade Jenkins Project Inheritance Plugin to version 2.0.1 or later, which properly respects the Mask Passwords Plugin's masking functionality for sensitive environment variables.

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
Project InheritanceApplication
Affected:<= 2.0.0

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. Identify if Jenkins Project Inheritance Plugin is installed
    Check for the presence of the plugin file: look for 'project-inheritance.jpi' or 'project-inheritance' folder in ${JENKINS_HOME}/plugins/ directory, or access Manage Jenkins > Manage Plugins > Installed and search for 'Project Inheritance'.
    Affected if The plugin is not found in the installed plugins list.
  2. Determine the installed version of Project Inheritance Plugin
    If the plugin is installed, check its version by examining the plugin's MANIFEST.MF file in ${JENKINS_HOME}/plugins/project-inheritance/META-INF/, or view the version displayed in the plugin manager UI.
    Affected if The version is 2.0.0 or earlier.
  3. Verify if Mask Passwords Plugin is also installed
    Check for the presence of 'mask-passwords.jpi' or 'mask-passwords' in ${JENKINS_HOME}/plugins/, or look for it in the installed plugins list in the Jenkins UI.
    Affected if The Mask Passwords Plugin is installed alongside the Project Inheritance Plugin.
  4. Check for sensitive environment variables in build output
    Run a build job that uses the Project Inheritance Plugin and includes password-type parameters or environment variables. Examine the build console output and the 'Environment Variables' section in the build page to see if sensitive values appear in plain text rather than masked.
    Affected if Sensitive values (passwords, credentials, secrets) are visible as unmasked plain text in build logs or environment variable displays.

You are affected if you have Jenkins Project Inheritance Plugin version 2.0.0 or earlier installed AND you use the Mask Passwords Plugin with sensitive environment variables that are displayed unmasked in build outputs.

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.0.0
Interim mitigation

Upgrade Jenkins Project Inheritance Plugin to version 2.0.1 or later, which properly respects the Mask Passwords Plugin's masking functionality for sensitive environment variables.

Fix this in Project Inheritance Scoped from the published advisory
  • Consultation1.0 h
  • Implementation0.5 h
  • Testing1.0 h
  • Review / QA0.5 h
3.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-10407 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