What is the severity of CVE-2022-45399?

CVE-2022-45399 is classified as a medium severity vulnerability due to the potential impact on Jenkins Cluster Statistics.

How do I fix CVE-2022-45399?

To fix CVE-2022-45399, upgrade to Cluster Statistics Plugin version 0.4.7 or later.

What is the cause of CVE-2022-45399?

CVE-2022-45399 is caused by a missing permission check in the Jenkins Cluster Statistics Plugin.

Who is affected by CVE-2022-45399?

Users of Jenkins Cluster Statistics Plugin version 0.4.6 and earlier are affected by CVE-2022-45399.

Vulnerability/
CVE-2022-45399

medium

4.3

CWE

862 352

15/11/2022

16/11/2022

21/11/2024

CVE-2022-45399: CSRF

Q: What is the impact of exploiting CVE-2022-45399?

Exploiting CVE-2022-45399 allows attackers to delete recorded Jenkins Cluster Statistics due to insufficient permissions.

First published: Tue Nov 15 2022(Updated: )

A missing permission check in Jenkins Cluster Statistics Plugin 0.4.6 and earlier allows attackers to delete recorded Jenkins Cluster Statistics.

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

Affected Software	Affected Version	How to fix
Jenkins Cluster Statistics	<=0.4.6
maven/org.zeroturnaround:cluster-stats	<=0.4.6
	<=0.4.6

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2022-45399?
CVE-2022-45399 is classified as a medium severity vulnerability due to the potential impact on Jenkins Cluster Statistics.
How do I fix CVE-2022-45399?
To fix CVE-2022-45399, upgrade to Cluster Statistics Plugin version 0.4.7 or later.
What is the cause of CVE-2022-45399?
CVE-2022-45399 is caused by a missing permission check in the Jenkins Cluster Statistics Plugin.
Who is affected by CVE-2022-45399?
Users of Jenkins Cluster Statistics Plugin version 0.4.6 and earlier are affected by CVE-2022-45399.
What is the impact of exploiting CVE-2022-45399?
Exploiting CVE-2022-45399 allows attackers to delete recorded Jenkins Cluster Statistics due to insufficient permissions.

collector/nvd-index
collector/github-advisory-latest
alias/GHSA-w8wg-62wf-62gm
alias/CVE-2022-45399
collector/nvd-cve
collector/github-advisory
agent/type
collector/mitre-cve
source/MITRE
agent/references
agent/weakness
agent/author
agent/severity
agent/description
agent/first-publish-date
collector/nvd-api
source/NVD
agent/software-canonical-lookup
agent/last-modified-date
agent/softwarecombine
agent/event
agent/trending
agent/tags
agent/source
vendor/jenkins
canonical/jenkins cluster statistics
version/jenkins cluster statistics/0.4.6
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-45399?
CVE-2022-45399 is classified as a medium severity vulnerability due to the potential impact on Jenkins Cluster Statistics.
How do I fix CVE-2022-45399?
To fix CVE-2022-45399, upgrade to Cluster Statistics Plugin version 0.4.7 or later.
What is the cause of CVE-2022-45399?
CVE-2022-45399 is caused by a missing permission check in the Jenkins Cluster Statistics Plugin.
Who is affected by CVE-2022-45399?
Users of Jenkins Cluster Statistics Plugin version 0.4.6 and earlier are affected by CVE-2022-45399.
What is the impact of exploiting CVE-2022-45399?
Exploiting CVE-2022-45399 allows attackers to delete recorded Jenkins Cluster Statistics due to insufficient permissions.