Security readout for executives and security teams
Plain-English summary
This Jenkins Perforce Plugin flaw can expose Perforce passwords stored in Jenkins jobs. An attacker with less access than should be required may be able to obtain those credentials, creating risk to source code and build integrity.
Executive priority
Treat as a credential exposure issue in CI/CD. Prioritize affected Jenkins systems that can access source code or production build pipelines.
Technical view
CVE-2018-1000147 affects Jenkins Perforce Plugin version 1.3.36 and older. The issue is in PerforcePasswordEncryptor.java and concerns exposure of Perforce passwords configured in jobs to attackers with insufficient permission.
Likely exposure
Exposure is likely limited to Jenkins environments using Perforce Plugin 1.3.36 or older with Perforce passwords configured in jobs.
Exploitation context
The provided sources do not report active exploitation, and KEV is false. The bundle does not specify public exploit availability or exact permission prerequisites.
Researcher notes
The source bundle lacks CVSS, CWE, fixed-version details, and precise authorization conditions. Analysis is therefore limited to the CVE description and Jenkins advisory reference.
Mitigation direction
- Inventory Jenkins Perforce Plugin versions across all controllers.
- Check Jenkins vendor advisory for the fixed or recommended plugin version.
- Upgrade affected Perforce Plugin installations following Jenkins guidance.
- Rotate Perforce passwords stored in affected Jenkins jobs.
- Review Jenkins job permissions for unnecessary access.
Validation and detection
- Confirm whether Perforce Plugin 1.3.36 or older is installed.
- Identify Jenkins jobs configured with Perforce passwords.
- Review access permissions for users who can view or configure affected jobs.
- Verify plugin update status after remediation.
- Confirm Perforce credential rotation where exposure was possible.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2018-1000147 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://jenkins.io/security/advisory/2018-03-26/#SECURITY-536CVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.