Github Pull Request BuilderApplication · Jenkins

CVE-2018-1000142

HIGH · 7.8 CVSS v3.0 Published 2018-04-05

Fix available

A fix is available. Upgrade to after 1.39.0 or later.

See remediation →

80/100

Remediation priority · High

Zero-click

Official description

NVD · unedited

An exposure of sensitive information vulnerability exists in Jenkins GitHub Pull Request Builder Plugin version 1.39.0 and older in GhprbCause.java that allows an attacker with local file system access to obtain GitHub credentials.

Technical summary

dbcve analysis · high confidence

The Jenkins GitHub Pull Request Builder Plugin versions 1.39.0 and older contains a file exposure vulnerability in GhprbCause.java that allows an attacker with local file system access to read stored GitHub credentials from the Jenkins environment.

MitigationUpgrade the GitHub Pull Request Builder Plugin to a version newer than 1.39.0 and rotate all GitHub credentials that may have been exposed.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

Github Pull Request BuilderApplication

Affected:<= 1.39.0

CVSS breakdown

From the vector

Attack vector: Local
Complexity: Low
Privileges: Low
User interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: High

CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected?

dbcve checks

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

Check if GitHub Pull Request Builder plugin is installed

Navigate to Jenkins > Manage Jenkins > Manage Plugins > Installed and search for 'GitHub Pull Request Builder' or 'ghprb'. Alternatively, check the plugin directory at $JENKINS_HOME/plugins for a folder starting with 'ghprb'.

Affected if The plugin is installed and present in the Jenkins plugins directory
Determine the installed version of the plugin

In Jenkins UI, go to Manage Jenkins > Manage Plugins > Installed and locate 'GitHub Pull Request Builder' in the list to view its version. If using CLI, inspect the plugin's manifest file at $JENKINS_HOME/plugins/ghprb/META-INF/MANIFEST.MF for the Plugin-Version attribute.

Affected if The version is 1.39.0 or older, or the version cannot be determined (older unversioned installations)
Verify if GitHub credentials are configured in Jenkins

Check for stored GitHub credentials in Jenkins > Credentials (look for credentials of type 'Username with password' or 'Secret text' that reference GitHub or GitHub API tokens). Also check the plugin configuration at Manage Jenkins > Configure System > GitHub Pull Request Builder for stored API tokens or OAuth tokens.

Affected if GitHub credentials (usernames, passwords, API tokens, or OAuth tokens) are stored in Jenkins credentials or plugin configuration
Check file permissions on Jenkins home directory

Review file permissions on $JENKINS_HOME and subdirectories, particularly $JENKINS_HOME/credentials.xml and $JENKINS_HOME/secrets/. Ensure world-readable or group-readable permissions exist that would allow local unprivileged users to access these files.

Affected if The Jenkins home directory or credential storage files have overly permissive access controls allowing unauthorized local file system access

A user is affected if the GitHub Pull Request Builder plugin version is 1.39.0 or older AND GitHub credentials are stored in the Jenkins environment, especially if the file system has permissive access controls.

Generated from the published advisory. Verify against your own configuration.

Remediation

From vendor data

Upgrade available Upgrade to a release after 1.39.0

Interim mitigation

Upgrade the GitHub Pull Request Builder Plugin to a version newer than 1.39.0 and rotate all GitHub credentials that may have been exposed.

Fix this in Github Pull Request Builder Scoped from the published advisory

Consultation2.0 h
Implementation2.0 h
Testing4.0 h
Review / QA2.0 h

10.0 hours of engineering $1,720

Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

jenkins.ioVendor Advisory
nvd.nist.govNVD record

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-1000142 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2018-1000142?

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.

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

At a glance

A fix existsUpgrade to after 1.39.0 or later

Severity 7.8 High

Exploit likelihood EPSS, next 30 days 0.4%

Affects: Github Pull Request Builder

Remediation

A high-priority fix

Fix this in Github Pull Request Builder 10 hrs · Moderate

Typical engagement from $1,720

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2018-1000142 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References