PerforceApplication
CVE-2018-1000147
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 exposure of sensitive information vulnerability exists in Jenkins Perforce Plugin version 1.3.36 and older in PerforcePasswordEncryptor.java that allows attackers with insufficient permission to obtain Perforce passwords configured in jobs to obtain them
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 Perforce Plugin versions 1.3.36 and older contains a vulnerability in PerforcePasswordEncryptor.java where password encryption is insufficient, allowing attackers with limited permissions to obtain Perforce passwords configured in Jenkins jobs. The encryption used for stored passwords can be reversed by unauthorized users.
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
PerforceApplication
<= 1.3.36CVSS 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.0/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 checksWork through these to decide whether this CVE applies to you.
-
Verify the Perforce Plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab, or check the $JENKINS_HOME/plugins directory for a perforce folder. Alternatively, access the Jenkins API: /pluginManager/plugin/{perforce}/api/jsonAffected if The Perforce plugin folder exists in the plugins directory or the API returns plugin information
-
Determine the installed version of the Perforce PluginIn the Jenkins UI, go to Manage Jenkins > Manage Plugins > Installed and locate the Perforce Plugin in the list to read the version number. Or examine the plugin manifest file at $JENKINS_HOME/plugins/perforce/META-INF/MANIFEST.MF for the Implementation-Version attributeAffected if The displayed version is 1.3.36 or any version lower than 1.3.36
-
Identify jobs using the Perforce PluginSearch Jenkins job configurations for Perforce-related build steps, or use the Jenkins API to query jobs that reference the perforce SCM type in their configuration XML. Check job config.xml files for <scm class="hudson.plugins.perforce..."/>Affected if Any Jenkins jobs are configured to use Perforce as an SCM or have Perforce build steps configured
-
Check for stored Perforce credentialsNavigate to Manage Jenkins > Manage Credentials to view all stored credentials. Look for Perforce credentials (username/password pairs) stored in any credential domain. Inspect the credentials.xml file in $JENKINS_HOME if direct file access is availableAffected if Perforce credentials (username/password) are stored in Jenkins credentials storage
You are affected if the Perforce Plugin version is 1.3.36 or lower AND you have jobs configured with Perforce SCM or have Perforce credentials stored in Jenkins.
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 Jenkins Perforce Plugin to a version newer than 1.3.36 and rotate all Perforce credentials that may have been exposed, as they could have been captured by prior unauthorized access.
Fix this in Perforce
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-1000147 — 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-2018-1000147 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