Security readout for executives and security teams
Plain-English summary
Jenkins Promoted Builds Plugin 2.31.1 and earlier let users with only job read access perform build promotions. If promotions control releases, approvals, or deployment gates, this could let a low-privileged user bypass intended workflow controls.
Executive priority
Treat as a workflow integrity issue. Prioritize remediation if Jenkins promotions approve releases, deployments, compliance gates, or production changes.
Technical view
The issue is an improper authorization flaw in Status.java and ManualCondition.java. The available CVE text states that attackers with read access to Jenkins jobs can perform promotions in affected Promoted Builds Plugin versions.
Likely exposure
Exposure is limited to Jenkins environments using Promoted Builds Plugin 2.31.1 or earlier where untrusted or broad user groups have job read access.
Exploitation context
The provided sources do not report active exploitation, and the CVE is not listed as KEV. Abuse requires job read access, but business impact depends on what promotions trigger.
Researcher notes
Evidence is sparse in the provided bundle: no CVSS, CWE, exploit detail, or fixed version is included. Analysis should stay tied to the stated authorization bypass and Jenkins advisory.
Mitigation direction
- Inventory Jenkins instances using Promoted Builds Plugin.
- Check whether plugin version is 2.31.1 or earlier.
- Review Jenkins advisory for vendor-approved fixed versions or guidance.
- Restrict job read access to trusted users only.
- Review promotion workflows tied to deployments or approvals.
Validation and detection
- Confirm installed Promoted Builds Plugin versions in Jenkins.
- Identify users and groups with job read permission.
- Review jobs where promotions trigger release or deployment actions.
- Check promotion history for unexpected low-privilege activity.
- Verify remediation against the Jenkins security advisory.
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-1000114 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-02-26/#SECURITY-746CVE 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.