CVE-2022-34818 — failedJobDeactivator
MEDIUMCVE-2022-34818 is a medium-severity (CVSS 4.3) CWE-862 vulnerability in de.einsundeins.jenkins.plugins.failedjobdeactivator:failedJobDeactivator. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.
Jenkins Failed Job Deactivator Plugin Missing Authorization vulnerability
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
de.einsundeins.jenkins.plugins.failedjobdeactivator:failedJobDeactivatorReal-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 Failed Job Deactivator Plugin 1.2.1 and earlier does not perform permission checks in several views and HTTP endpoints.
This allows attackers with Overall/Read permission to disable jobs.
Additionally, these endpoints do not require POST requests, resulting in a cross-site request forgery (CSRF) vulnerability.
As of publication of this advisory, there is no fix.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | de.einsundeins.jenkins.plugins.failedjobdeactivator:failedJobDeactivator | all versions | No fix |
Affected Products
failed job deactivatorjenkinsDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for de.einsundeins.jenkins.plugins.failedjobdeactivator:failedJobDeactivator, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of de.einsundeins.jenkins.plugins.failedjobdeactivator:failedJobDeactivator for CVE-2022-34818. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
Frequently Asked Questions
Is CVE-2022-34818 in your dependencies?
Find it across Maven, including transitive dependencies.