Security readout for executives and security teams
Plain-English summary
This Jenkins plugin flaw could let a low-privileged Jenkins user abuse the GitHub Pull Request Builder Plugin to make Jenkins send stored credentials to a URL they control. The attacker still needs Overall/Read access and credential IDs obtained another way, but the business impact can include CI credential theft and downstream repository or service compromise.
Executive priority
Treat this as a high-priority CI credential exposure issue, not just a plugin bug. Prioritize internet-facing or shared Jenkins controllers first, then rotate credentials that could grant repository, deployment, or cloud access.
Technical view
CVE-2018-1000186 affects Jenkins GitHub Pull Request Builder Plugin 1.41.0 and older. In GhprbGitHubAuth.java, users with Overall/Read can connect to an attacker-specified URL using attacker-specified Jenkins credential IDs obtained separately, allowing captured Jenkins-stored credentials. The source bundle provides no CVSS score or CWE.
Likely exposure
Exposure is limited to Jenkins environments running GitHub Pull Request Builder Plugin 1.41.0 or older, especially where untrusted users have Overall/Read access and credential IDs are discoverable through another path.
Exploitation context
The provided sources do not show CISA KEV listing or active exploitation. Exploitation is described as authenticated and conditional: the attacker needs Overall/Read access plus credential IDs from another method, then can direct Jenkins credential use toward an attacker-controlled URL.
Researcher notes
The key constraints are important: Overall/Read access is required, and credential IDs must be obtained through another method. The bundle does not provide a CVSS score, exploit proof, fixed version number, or evidence of active exploitation.
Mitigation direction
- Check Jenkins advisory SECURITY-805 and plugin guidance for the fixed version.
- Upgrade or remove affected GitHub Pull Request Builder Plugin installations.
- Restrict Overall/Read access to trusted Jenkins users only.
- Rotate Jenkins credentials that may have been exposed through the plugin.
- Review Jenkins credential ID visibility and reduce unnecessary disclosure.
Validation and detection
- Inventory Jenkins controllers for GitHub Pull Request Builder Plugin versions.
- Flag plugin versions 1.41.0 and older as affected.
- Review users and groups granted Jenkins Overall/Read permission.
- Check Jenkins logs for unexpected outbound connections from this plugin path.
- Confirm potentially exposed Jenkins credentials have been rotated.
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-1000186 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-06-04/#SECURITY-805CVE 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.