CVE-2017-1000110: Improper Authentication in Jenkins Blue Ocean Plugin

CVE-2017-1000110 · Severity: low · CVSS 3 · Published 2022-05-13

Improper Authentication in Jenkins Blue Ocean Plugin

Technologies: io.jenkins.blueocean:blueocean (Maven). Vendors: Maven.

Quick answers

Is CVE-2017-1000110 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2017-1000110 being exploited in the wild.
How severe is CVE-2017-1000110?
Low severity, with a CVSS score of 3, published 13 May 2022.
Which products and versions are affected?
io.jenkins.blueocean:blueocean (Maven) ECOSYSTEM:introduced=0,fixed=1.2.0.
Is there a fix for CVE-2017-1000110?
Yes. io.jenkins.blueocean:blueocean (Maven): upgrade to 1.2.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2017-1000110?
Check whether you run io.jenkins.blueocean:blueocean (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

  • io.jenkins.blueocean:blueocean (Maven): upgrade to 1.2.0 or later
    # set io.jenkins.blueocean:blueocean to 1.2.0 in your pom.xml or build.gradle

Affected products

  • io.jenkins.blueocean:blueocean (Maven) ECOSYSTEM:introduced=0,fixed=1.2.0

Identifiers

  • CVE-2017-1000110
  • GHSA-rm5m-9mx4-g5r7

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