Security readout for executives and security teams
Plain-English summary
This issue can let a low-privileged Jenkins user steal stored Jenkins credentials from installations using Black Duck Hub Plugin 4.0.0 or older. The attacker needs Jenkins Overall/Read access and a credential ID obtained separately. Business risk is highest where Jenkins credentials can reach source code, build artifacts, cloud accounts, or deployment systems.
Executive priority
Prioritize remediation where Jenkins has deployment, cloud, repository, or artifact credentials. The issue is narrower than internet-scale remote compromise, but credential theft from CI/CD can quickly become a broader business incident.
Technical view
Jenkins Black Duck Hub Plugin 4.0.0 and older has a sensitive information exposure in PostBuildScanDescriptor.java. A user with Overall/Read can cause Jenkins to connect to an attacker-controlled URL using a chosen stored credentials ID, allowing credential capture. The source bundle does not provide CVSS, CWE, exploit code, or a named fixed version.
Likely exposure
Exposure is limited to Jenkins controllers with Black Duck Hub Plugin 4.0.0 or older installed. Risk increases when non-admin users have Overall/Read, credential IDs are discoverable, or Jenkins credentials have broad downstream access.
Exploitation context
The provided sources do not show known active exploitation, and the CVE is not marked KEV. Exploitation is not anonymous: it requires Overall/Read access and a credential ID learned through another method.
Researcher notes
The strongest evidence is the CVE description and Jenkins advisory reference. Missing details include CVSS, CWE, exact fixed version, and exploitation reports. Treat upgrade and mitigation direction as dependent on Jenkins or plugin vendor guidance.
Mitigation direction
- Inventory Jenkins controllers for Black Duck Hub Plugin 4.0.0 or older.
- Check Jenkins advisory and vendor guidance for fixed versions or official mitigation.
- Restrict Jenkins Overall/Read to trusted users only.
- Rotate potentially exposed Jenkins credentials after confirming exposure risk.
- Limit credential scope to the minimum required downstream systems.
Validation and detection
- Confirm whether the Black Duck Hub Plugin is installed and its version.
- Review Jenkins permission assignments for users with Overall/Read.
- Identify stored credentials referenced by Black Duck Hub Plugin configuration.
- Check Jenkins and network logs for unexpected outbound connections.
- Review whether credential IDs were exposed through jobs, logs, or configuration.
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-1000190 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-865CVE 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.