Synopsys DetectApplication · Jenkins
CVE-2018-1000191
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA exposure of sensitive information vulnerability exists in Jenkins Black Duck Detect Plugin 1.4.0 and older in DetectPostBuildStepDescriptor.java that allows attackers with Overall/Read access to connect to an attacker-specified URL using attacker-specified credentials IDs obtained through another method, capturing credentials stored in Jenkins.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Jenkins Black Duck Detect Plugin versions 1.4.0 and older allows attackers with Overall/Read access to specify an arbitrary URL and credential IDs through the plugin's build step. When Jenkins processes these requests, it sends the configured credentials to the attacker-controlled URL, resulting in credential exfiltration. This is a combination of Server-Side Request Forgery (SSRF) enabling credential theft.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Synopsys DetectApplication
<= 1.4.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Black Duck Detect Plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed and search for 'Black Duck Detect' or 'Synopsys Detect'. Note the installed version.Affected if Plugin version is 1.4.0 or older (or plugin is present with no version visible, treat as potentially affected)
-
Confirm Overall/Read access scopeNavigate to Manage Jenkins > Manage Users and review user accounts. Check Manage Jenkins > Configure Global Security to see who is granted Overall/Read permission.Affected if Any untrusted or non-admin users have Overall/Read access in a multi-user Jenkins instance
-
Inspect build jobs using the pluginReview Jenkins jobs that use the Black Duck Detect/Synopsys Detect build step. Navigate to each job > Configure and look for 'Black Duck' or 'Synopsys Detect' in the Build section.Affected if Any job is configured with a Black Duck Detect build step
-
Review configured credentials and URLsIn jobs using the plugin, examine the 'Black Duck Hub' or 'Synopsys Detect' configuration fields for 'Hub URL', 'API token', or credential bindings.Affected if Jobs contain hardcoded URLs pointing to unexpected external domains or credential IDs pointing to sensitive credentials
If the Black Duck Detect Plugin version is 1.4.0 or older AND untrusted users have Overall/Read access AND jobs use this plugin, the environment is vulnerable to SSRF-driven credential theft.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade the Black Duck Detect Plugin to a version newer than 1.4.0. If no patched version is available, immediately revoke Overall/Read access from untrusted users and review stored credentials for potential compromise.
Fix this in Synopsys Detect
Scoped from the published advisory
- Consultation3.0 h
- Implementation2.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,840.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-1000191 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-1000191 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data