First published: Wed Sep 16 2020(Updated: )
Email Extension Plugin 2.75 and earlier does not perform hostname validation when connecting to the configured SMTP server. This lack of validation could be abused using a man-in-the-middle attack to intercept these connections. Email Extension Plugin 2.76 validates the SMTP hostname when connecting via TLS by default. In Email Extension Plugin 2.75 and earlier, administrators can set the Java system property `mail.smtp.ssl.checkserveridentity` to `true` on startup to enable this protection. Alternatively, this protection can be enabled (or disabled in the new version) via the 'Advanced Email Properties' field in the plugin’s configuration in Configure System. In case of problems, this protection can be disabled again by setting `mail.smtp.ssl.checkserveridentity` to `false` using either method.
Credit: jenkinsci-cert@googlegroups.com jenkinsci-cert@googlegroups.com jenkinsci-cert@googlegroups.com
Affected Software | Affected Version | How to fix |
---|---|---|
Jenkins Email Extension | <=2.75 | |
maven/org.jenkins-ci.plugins:email-ext | <=2.75 | 2.76 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2020-2253 is a vulnerability in Jenkins Email Extension Plugin 2.75 and earlier versions that allows man-in-the-middle attacks.
CVE-2020-2253 has a severity rating of medium.
Jenkins Email Extension Plugin versions 2.75 and earlier versions are affected by CVE-2020-2253.
CVE-2020-2253 can be exploited by performing a man-in-the-middle attack to intercept the connections.
Yes, the fix for CVE-2020-2253 is available in Email Extension Plugin version 2.76.