Security readout for executives and security teams
Plain-English summary
Jenkins installations using Black Duck Hub Plugin 3.1.0 or older may let a logged-in user with Overall/Read permission cause Jenkins to process external XML entities. In business terms, this is a plugin-level data exposure and internal request risk, not a confirmed internet-wide emergency from the provided evidence.
Executive priority
Treat this as a targeted Jenkins plugin remediation item. Prioritize environments where Jenkins contains sensitive build secrets, has network reachability to internal systems, or grants read access broadly.
Technical view
The vulnerability is XXE processing in PostBuildScanDescriptor.java in Jenkins Black Duck Hub Plugin 3.1.0 and earlier. An attacker with Overall/Read permission can submit XML that makes Jenkins process external entities. The source bundle does not provide CVSS, CWE, patch version, impact detail, or proof of exploitation.
Likely exposure
Exposure is limited to Jenkins environments that installed Black Duck Hub Plugin 3.1.0 or older and grant Overall/Read to untrusted or broadly trusted users. Systems without this plugin, or with tighter Jenkins read access, are less likely to be exposed.
Exploitation context
The provided sources do not show CISA KEV listing or active exploitation. Exploitation requires at least Overall/Read permission, so the main concern is authenticated misuse in Jenkins environments where read access is widely distributed.
Researcher notes
Evidence is sparse: affected component, version ceiling, permission prerequisite, and XXE class are clear, but impact boundaries and fixed version are not included in the bundle. Avoid assuming file disclosure, SSRF, or patch details without vendor advisory confirmation.
Mitigation direction
- Inventory Jenkins controllers for Black Duck Hub Plugin usage and version.
- Check Jenkins advisory and vendor guidance for the fixed or recommended plugin version.
- Update, disable, or remove the plugin according to vendor guidance.
- Limit Overall/Read permission to trusted users where operationally possible.
- Review Jenkins access groups for broad or stale read access.
Validation and detection
- Confirm whether Black Duck Hub Plugin is installed on each Jenkins controller.
- Verify installed plugin versions are not 3.1.0 or older.
- Review Jenkins authorization settings for users with Overall/Read permission.
- Check Jenkins logs for suspicious plugin configuration or XML-processing activity.
- Document compensating controls if immediate update or removal is not 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-1000198 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-05-09/#SECURITY-671CVE 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.