CVE-2017-2651: Exposure of Sensitive Information to an Unauthorized Actor in Jenkins-mailer-plugin

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

Exposure of Sensitive Information to an Unauthorized Actor in Jenkins-mailer-plugin

Technologies: org.jenkins-ci.plugins:mailer (Maven). Vendors: Maven.

Quick answers

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

  • org.jenkins-ci.plugins:mailer (Maven): upgrade to 1.20 or later
    # set org.jenkins-ci.plugins:mailer to 1.20 in your pom.xml or build.gradle

Affected products

  • org.jenkins-ci.plugins:mailer (Maven) ECOSYSTEM:introduced=0,fixed=1.20

Identifiers

  • CVE-2017-2651
  • GHSA-9v72-p5p3-9w65

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