CVE-2022-20612 is a medium-severity (CVSS 4.3) Cross-Site Request Forgery (CSRF) vulnerability in org.jenkins-ci.main:jenkins-core. A fix is available for org.jenkins-ci.main:jenkins-core — see the affected versions and patch details below.
Cross-Site Request Forgery in Jenkins
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2022-20612 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,386 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
org.jenkins-ci.main:jenkins-core☕org.jenkins-ci.main:jenkins-coreReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.jenkins-ci.main:jenkins-core | ≥ 2.320&&< 2.330 | 2.330org.jenkins-ci.main:jenkins-core:2.330 |
| ☕Maven | org.jenkins-ci.main:jenkins-core | all versions | 2.319.2org.jenkins-ci.main:jenkins-core:2.319.2 |
Affected Products
jenkinsjenkinscommunications cloud native core automated test suiteoracleDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.main:jenkins-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jenkins-ci.main:jenkins-core to 2.330 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-20612 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat OpenShift Container Platform 3.11 | jenkins-0:2.319.2.1644411558-1.el7 | RHSA-2022:0555 |
| Red Hat OpenShift Container Platform 4.10 | jenkins-0:2.319.2.1643288987-1.el8 | RHSA-2022:0055 |
| Red Hat OpenShift Container Platform 4.6 | jenkins-0:2.319.2.1643964085-1.el8 | RHSA-2022:0565 |
| Red Hat OpenShift Container Platform 4.7 | jenkins-0:2.319.2.1643882372-1.el8 | RHSA-2022:0491 |
| Red Hat OpenShift Container Platform 4.8 | jenkins-0:2.319.2.1643648617-1.el8 | RHSA-2022:0483 |
| Red Hat OpenShift Container Platform 4.9 | jenkins-0:2.319.2.1643391771-1.el8 | RHSA-2022:0339 |
Frequently Asked Questions
Is CVE-2022-20612 in your dependencies?
Find it across Maven, including transitive dependencies.