Security readout for executives and security teams
Plain-English summary
CVE-2018-1000145 affects Jenkins Perforce Plugin 1.3.36 and older. A person who already has local filesystem access to the Jenkins host can recover encrypted Perforce passwords and decrypt them, potentially exposing source-control credentials.
Executive priority
Treat this as a credential-protection issue for Jenkins and Perforce. Prioritize environments where Jenkins has broad source-control access or where many administrators, build users, or backup processes can read Jenkins files.
Technical view
The vulnerability is in PerforcePasswordEncryptor.java in Jenkins Perforce Plugin 1.3.36 and older. The source states local filesystem access is required to obtain encrypted Perforce passwords and decrypt them. No CVSS, CWE, or detailed fixed version is provided in the bundle.
Likely exposure
Exposure is most likely on Jenkins instances running the legacy Perforce Plugin 1.3.36 or older and storing Perforce credentials. Risk depends on who can read Jenkins files on the controller or relevant filesystem backups.
Exploitation context
The bundle does not report active exploitation and KEV is false. The stated prerequisite is local filesystem access, so this is mainly a post-compromise or insider-access credential exposure risk rather than a remote-first issue.
Researcher notes
Evidence is limited to the CVE description and Jenkins advisory reference. The bundle names the vulnerable component and access condition but does not include CVSS, CWE, exploit evidence, or explicit remediation details.
Mitigation direction
- Identify Jenkins instances using the Perforce Plugin version 1.3.36 or older.
- Review the Jenkins advisory and plugin manager for the vendor-supported update path.
- Restrict local filesystem access to Jenkins home, configuration, backups, and credential files.
- Rotate exposed Perforce credentials after remediation if filesystem access may have occurred.
Validation and detection
- Inventory installed Jenkins Perforce Plugin versions across production and build environments.
- Check whether Jenkins stores Perforce credentials on affected instances.
- Review filesystem permissions and backup access for Jenkins credential-related data.
- Look for local user or service-account access to Jenkins files during the exposure window.
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-1000145 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-373CVE 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.