What is the severity of CVE-2022-34818?

CVE-2022-34818 is considered a medium severity vulnerability due to permissions flaws that allow unauthorized job deactivation.

How do I fix CVE-2022-34818?

To fix CVE-2022-34818, upgrade the Jenkins Failed Job Deactivator Plugin to version 1.2.2 or later.

Who is affected by CVE-2022-34818?

Any Jenkins instance using the Failed Job Deactivator Plugin version 1.2.1 or earlier is affected by CVE-2022-34818.

What are the consequences of CVE-2022-34818?

The consequences of CVE-2022-34818 include the potential for attackers to disable jobs without proper authorization.

What does CVE-2022-34818 exploit?

CVE-2022-34818 exploits the lack of permission checks in various views and HTTP endpoints within the Jenkins Failed Job Deactivator Plugin.

Vulnerability/
CVE-2022-34818

medium

4.3

CWE

862 352

30/6/2022

1/7/2022

3/8/2024

CVE-2022-34818: CSRF

First published: Thu Jun 30 2022(Updated: )

Jenkins Failed Job Deactivator Plugin 1.2.1 and earlier does not perform permission checks in several views and HTTP endpoints, allowing attackers with Overall/Read permission to disable jobs.

Credit: jenkinsci-cert@googlegroups.com jenkinsci-cert@googlegroups.com jenkinsci-cert@googlegroups.com

Affected Software	Affected Version	How to fix
Jenkins Failed Job Deactivator	<=1.2.1
maven/de.einsundeins.jenkins.plugins.failedjobdeactivator:failedJobDeactivator	<=1.2.1

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2022-34818?
CVE-2022-34818 is considered a medium severity vulnerability due to permissions flaws that allow unauthorized job deactivation.
How do I fix CVE-2022-34818?
To fix CVE-2022-34818, upgrade the Jenkins Failed Job Deactivator Plugin to version 1.2.2 or later.
Who is affected by CVE-2022-34818?
Any Jenkins instance using the Failed Job Deactivator Plugin version 1.2.1 or earlier is affected by CVE-2022-34818.
What are the consequences of CVE-2022-34818?
The consequences of CVE-2022-34818 include the potential for attackers to disable jobs without proper authorization.
What does CVE-2022-34818 exploit?
CVE-2022-34818 exploits the lack of permission checks in various views and HTTP endpoints within the Jenkins Failed Job Deactivator Plugin.

collector/nvd-index
collector/github-advisory-latest
alias/GHSA-hcjr-6jq3-392p
alias/CVE-2022-34818
collector/nvd-cve
collector/github-advisory
collector/nvd-api
agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/author
agent/references
agent/weakness
agent/severity
agent/last-modified-date
agent/event
agent/description
agent/first-publish-date
agent/trending
agent/tags
agent/source
vendor/jenkins
canonical/jenkins failed job deactivator
version/jenkins failed job deactivator/1.2.1
package-manager/maven

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2022-34818?
CVE-2022-34818 is considered a medium severity vulnerability due to permissions flaws that allow unauthorized job deactivation.
How do I fix CVE-2022-34818?
To fix CVE-2022-34818, upgrade the Jenkins Failed Job Deactivator Plugin to version 1.2.2 or later.
Who is affected by CVE-2022-34818?
Any Jenkins instance using the Failed Job Deactivator Plugin version 1.2.1 or earlier is affected by CVE-2022-34818.
What are the consequences of CVE-2022-34818?
The consequences of CVE-2022-34818 include the potential for attackers to disable jobs without proper authorization.
What does CVE-2022-34818 exploit?
CVE-2022-34818 exploits the lack of permission checks in various views and HTTP endpoints within the Jenkins Failed Job Deactivator Plugin.