XML External Entity processing vulnerability in Jenkins Black Duck Hub Plugin

published 2018-06-05 8y ago modified 2026-06-17 4mo ago also GHSA-8rc4-3jc3-83pm , EUVD-2022-3225

cvss: 6.5; version 3.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 1.0%; EPSS 1.0% chance of exploitation in 30 days, percentile 61%
public exploits: 0; none known

A 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.

Patch / fix

fixed in 1

maven com.blackducksoftware.integration:blackduck-hub 4.0.0

Is CVE-2018-1000198 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.95% chance of exploitation in the next 30 days, higher than 61% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.0	6.5	CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
NVD	2.0	4.0	AV:N/AC:L/Au:S/C:P/I:N/A:N
GitHub	3.0	6.5	CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem	package	affected	fixed in
maven	com.blackducksoftware.integration:blackduck-hub	<4.0.0	4.0.0

Classification

Weakness

CWE-611 Improper Restriction of XML External Entity Reference

References

jenkins.io /security/advisory/2018-05-09/#SECURITY-671
web, vendor-advisory
nvd.nist.gov /vuln/detail/CVE-2018-1000198
advisory

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.