How severe is CVE-2018-1000197?

CVE-2018-1000197 has a CVSS score of 8.1/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2018-1000197?

CVE-2018-1000197 affects the following packages: com.blackducksoftware.integration:blackduck-hub (Maven). Ecosystems affected: Maven.

How do I fix CVE-2018-1000197?

Update com.blackducksoftware.integration:blackduck-hub to 3.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-1000197 is resolved across your whole dependency graph.

How do I detect CVE-2018-1000197 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.blackducksoftware.integration:blackduck-hub, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2018-1000197 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is CVE-2018-1000197 actively exploited in the wild?

No public exploit code has been indexed for CVE-2018-1000197 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2018-1000197?

CVE-2018-1000197 has an EPSS (Exploit Prediction Scoring System) score of 0.8%, placing it in the 58th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2018-1000197?

CVE-2018-1000197 is classified as CWE-863 (CWE-863). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2018-1000197 published, and has it been updated?

CVE-2018-1000197 was published on June 5, 2018 and was last updated on October 24, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

HIGH severity

CVE-2018-1000197 — blackduck-hub

HIGH

CVE-2018-1000197 is a high-severity (CVSS 8.1) CWE-863 vulnerability in com.blackducksoftware.integration:blackduck-hub. A fix is available for com.blackducksoftware.integration:blackduck-hub — see the affected versions and patch details below.

Jenkins Black Duck Hub Plugin allowed any user with Overall/Read to read and write its configuration

Also known asGHSA-crvq-mw2w-4cfx

Published

Jun 5, 2018

Updated

Oct 24, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

0.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs58th percentile — riskier than 58% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

☕com.blackducksoftware.integration:blackduck-hub

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

An improper authorization vulnerability exists in Jenkins Black Duck Hub Plugin 3.0.3 and older in PostBuildScanDescriptor.java that allows users with Overall/Read permission to read and write the Black Duck Hub plugin configuration.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.blackducksoftware.integration:blackduck-hub`	all versions	3.1.0`com.blackducksoftware.integration:blackduck-hub:3.1.0`

Affected Products

1 product · 1 configurations

Application

black duck hubjenkins

≤ 3.0.3

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.blackducksoftware.integration:blackduck-hub, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.blackducksoftware.integration:blackduck-hub to 3.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-1000197 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2018-1000197 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

8.1/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

None

Raw vector

CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

CWE Classification

CWE-863CWE-863

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

Timeline

Disclosed

Jun 5, 2018

Last updated

Oct 24, 2026

Identifiers

CVE-2018-1000197

GHSA-crvq-mw2w-4cfx

References

Advisoryjenkins.io · 2018 05 09 Advisorynvd.nist.gov · CVE 2018 1000197

Related vulnerabilities

Also affects blackduck-hub

This CVE is high severity — higher than any of the other 2 CVEs affecting blackduck-hub (highest there: moderate).

CVE-2018-1000190CVE-2018-1000198

Same weakness: CWE-863

This CVE is high severity; 2 of 6 other CVEs with CWE-863 are rated as high or higher (top: high).

CVE-2026-55098GHSA-j656-3hf2-fvjcCVE-2026-118669CVE-2026-119200GHSA-fgxm-5hvv-x4vhCVE-2026-63414Browse all CWE-863

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 24, 2026