CVE-2022-20612

Cross-Site Request Forgery in Jenkins

Jenkins 2.329 and earlier, LTS 2.319.1 and earlier does not require POST requests for the HTTP endpoint handling manual build requests when no security realm is set, resulting in a cross-site request forgery (CSRF) vulnerability.

This vulnerability allows attackers to trigger build of job without parameters.

Jenkins 2.330, LTS 2.319.2 requires POST requests for the affected HTTP endpoint.

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-20612 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 (2.319.2, 2.330); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2022-20612? CVE-2022-20612 is a medium-severity cross-site request forgery (CSRF) vulnerability in org.jenkins-ci.main:jenkins-core (maven), affecting versions < 2.319.2. It is fixed in 2.319.2, 2.330. 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-20612? CVE-2022-20612 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.main:jenkins-core are affected by CVE-2022-20612? org.jenkins-ci.main:jenkins-core (maven) versions < 2.319.2 is affected.
4. Is there a fix for CVE-2022-20612? Yes. CVE-2022-20612 is fixed in 2.319.2, 2.330. Upgrade to this version or later.
5. Is CVE-2022-20612 exploitable, and should I be worried? Whether CVE-2022-20612 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-20612 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-20612?
   • Upgrade org.jenkins-ci.main:jenkins-core to 2.319.2 or later
   • Upgrade org.jenkins-ci.main:jenkins-core to 2.330 or later

Other vulnerabilities in org.jenkins-ci.main:jenkins-core