Black Duck HubApplication · Jenkins
CVE-2018-1000198
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 XML external entity processing vulnerability exists in Jenkins Black Duck Hub Plugin 3.1.0 and older in PostBuildScanDescriptor.java that allows attackers with Overall/Read permission to make Jenkins process XML eternal entities in an XML document.
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 confidenceAn XML external entity (XXE) vulnerability exists in Jenkins Black Duck Hub Plugin version 3.1.0 and older in the PostBuildScanDescriptor.java file. Attackers with Overall/Read permission can craft malicious XML documents containing external entity references that Jenkins will process, potentially exposing sensitive files, internal resources, or causing denial of service.
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
Black Duck HubApplication
<= 3.1.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.
-
Confirm Black Duck Hub Plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab and search for 'Black Duck Hub' or 'blackduck-hub-plugin' in the list of installed pluginsAffected if The Black Duck Hub Plugin appears in the installed plugins list
-
Identify installed Black Duck Hub Plugin versionIn the Installed plugins tab, locate the Black Duck Hub Plugin and note the Version column valueAffected if The version listed is 3.1.0 or any version lower (e.g., 3.1.0, 3.0.9, 2.x, 1.x)
-
Verify Overall/Read permission is activeNavigate to Jenkins > Manage Jenkins > Manage Users and check user accounts, or go to Manage Jenkins > Configure Global Security to review Authorization settings. In a default Jenkins setup, Overall/Read is granted to authenticated users or anonymous users.Affected if Any user account (including limited or build-only users) has Overall/Read permission, which is the default permission in Jenkins
-
Confirm the XXE-prone code path existsThe vulnerability is in PostBuildScanDescriptor.java within the plugin. This check verifies plugin presence and version only; the vulnerable code is present in all versions 3.1.0 and older.Affected if Steps 1-3 confirm the plugin is installed at version 3.1.0 or older with Overall/Read permission enabled for at least one user
A user is affected if the Black Duck Hub Plugin version 3.1.0 or older is installed on Jenkins and any user (including those with minimal permissions) has Overall/Read access, allowing them to trigger the XXE vulnerability.
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 dataUpdate to a patched version of the Black Duck Hub Plugin (3.1.1 or newer). As a compensating control, restrict Overall/Read permission to only necessary users until the patch can be applied.
Fix this in Black Duck Hub
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-1000198 — 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-1000198 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