CVE-2018-1000190: Exposure of sensitive information vulnerability in Jenkins Black Duck Hub Plugin

CVE-2018-1000190 · Severity: low · CVSS 3 · Published 2022-05-14

Exposure of sensitive information vulnerability in Jenkins Black Duck Hub Plugin

Technologies: com.blackducksoftware.integration:blackduck-hub (Maven). Vendors: Maven.

Quick answers

Is CVE-2018-1000190 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2018-1000190 being exploited in the wild.
How severe is CVE-2018-1000190?
Low severity, with a CVSS score of 3, published 14 May 2022.
Which products and versions are affected?
com.blackducksoftware.integration:blackduck-hub (Maven) ECOSYSTEM:introduced=0,fixed=4.0.1.
Is there a fix for CVE-2018-1000190?
Yes. com.blackducksoftware.integration:blackduck-hub (Maven): upgrade to 4.0.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2018-1000190?
Check whether you run com.blackducksoftware.integration:blackduck-hub (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • com.blackducksoftware.integration:blackduck-hub (Maven): upgrade to 4.0.1 or later
    # set com.blackducksoftware.integration:blackduck-hub to 4.0.1 in your pom.xml or build.gradle

Affected products

  • com.blackducksoftware.integration:blackduck-hub (Maven) ECOSYSTEM:introduced=0,fixed=4.0.1

Identifiers

  • CVE-2018-1000190
  • GHSA-26hw-262c-g9gc

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.