CVE-2018-1000609: Jenkins Configuration as Code Plugin vulnerable to Exposure of Sensitive Information

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

Jenkins Configuration as Code Plugin vulnerable to Exposure of Sensitive Information

Technologies: io.jenkins:configuration-as-code (Maven). Vendors: Maven.

Quick answers

Is CVE-2018-1000609 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2018-1000609 being exploited in the wild.
How severe is CVE-2018-1000609?
Low severity, with a CVSS score of 3, published 14 May 2022.
Which products and versions are affected?
io.jenkins:configuration-as-code (Maven) ECOSYSTEM:introduced=0,fixed=0.8-alpha.
Is there a fix for CVE-2018-1000609?
Yes. io.jenkins:configuration-as-code (Maven): upgrade to 0.8-alpha or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2018-1000609?
Check whether you run io.jenkins:configuration-as-code (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:configuration-as-code (Maven): upgrade to 0.8-alpha or later
    # set io.jenkins:configuration-as-code to 0.8-alpha in your pom.xml or build.gradle

Affected products

  • io.jenkins:configuration-as-code (Maven) ECOSYSTEM:introduced=0,fixed=0.8-alpha

Identifiers

  • CVE-2018-1000609
  • GHSA-393r-r9mq-g9jv

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