CVE-2022-20613

Cross-Site Request Forgery in Jenkins Mailer Plugin

Jenkins Mailer Plugin prior to 408.vd726a_1130320 and 1.34.2 does not perform a permission check in a method implementing form validation.

This allows attackers with Overall/Read access to use the DNS used by the Jenkins instance to resolve an attacker-specified hostname.

Additionally, this form validation method does not require POST requests, resulting in a cross-site request forgery (CSRF) vulnerability.

Mailer Plugin 408.vd726a_1130320 and 1.34.2 require POST requests and Overall/Administer permission for the affected form validation method.

A victim's authenticated browser session is used to submit forged requests to an application that cannot distinguish them from legitimate ones. Typical impact: state-changing actions performed as the victim without their consent.

CVE-2022-20613 has a CVSS score of 4.3 (Medium). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (408.vd726a, 1.34.2); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

1. What is CVE-2022-20613? CVE-2022-20613 is a medium-severity cross-site request forgery (CSRF) vulnerability in org.jenkins-ci.plugins:mailer (maven), affecting versions >= 391.ve4a38c1bcf4b, < 408.vd726a. It is fixed in 408.vd726a, 1.34.2. A victim's authenticated browser session is used to submit forged requests to an application that cannot distinguish them from legitimate ones.
2. How severe is CVE-2022-20613? CVE-2022-20613 has a CVSS score of 4.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of org.jenkins-ci.plugins:mailer are affected by CVE-2022-20613? org.jenkins-ci.plugins:mailer (maven) versions >= 391.ve4a38c1bcf4b, < 408.vd726a is affected.
4. Is there a fix for CVE-2022-20613? Yes. CVE-2022-20613 is fixed in 408.vd726a, 1.34.2. Upgrade to this version or later.
5. Is CVE-2022-20613 exploitable, and should I be worried? Whether CVE-2022-20613 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2022-20613 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2022-20613?
   • Upgrade org.jenkins-ci.plugins:mailer to 408.vd726a or later
   • Upgrade org.jenkins-ci.plugins:mailer to 1.34.2 or later

Other vulnerabilities in org.jenkins-ci.plugins:mailer