What is the severity of CVE-2022-45394?

CVE-2022-45394 is classified as a critical vulnerability due to its potential impact on sensitive build logs.

How do I fix CVE-2022-45394?

To fix CVE-2022-45394, upgrade to a version of the Jenkins Delete log Plugin that is newer than 1.0.

What causes CVE-2022-45394?

CVE-2022-45394 is caused by a missing permission check that allows users with Item/Read permission to delete build logs.

Which versions of Jenkins are affected by CVE-2022-45394?

Versions of the Jenkins Delete log Plugin prior to 1.0 are affected by CVE-2022-45394.

What can attackers do with CVE-2022-45394?

Attackers can exploit CVE-2022-45394 to delete build logs if they have Item/Read permissions.

Vulnerability/
CVE-2022-45394

medium

4.3

CWE

862

15/11/2022

16/11/2022

21/11/2024

CVE-2022-45394

First published: Tue Nov 15 2022(Updated: )

A missing permission check in Jenkins Delete log Plugin 1.0 and earlier allows attackers with Item/Read permission to delete build logs.

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

Affected Software	Affected Version	How to fix
maven/org.jenkins-ci.plugins:delete-log-plugin	<=1.0
Jenkins	<=1.0

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2022-45394?
CVE-2022-45394 is classified as a critical vulnerability due to its potential impact on sensitive build logs.
How do I fix CVE-2022-45394?
To fix CVE-2022-45394, upgrade to a version of the Jenkins Delete log Plugin that is newer than 1.0.
What causes CVE-2022-45394?
CVE-2022-45394 is caused by a missing permission check that allows users with Item/Read permission to delete build logs.
Which versions of Jenkins are affected by CVE-2022-45394?
Versions of the Jenkins Delete log Plugin prior to 1.0 are affected by CVE-2022-45394.
What can attackers do with CVE-2022-45394?
Attackers can exploit CVE-2022-45394 to delete build logs if they have Item/Read permissions.

collector/github-advisory-latest
alias/GHSA-j874-47xx-9xfg
alias/CVE-2022-45394
agent/type
agent/references
collector/mitre-cve
source/MITRE
agent/weakness
agent/severity
agent/author
agent/first-publish-date
agent/description
agent/last-modified-date
agent/softwarecombine
agent/event
agent/trending
agent/source
agent/tags
collector/nvd-api
source/NVD
agent/software-canonical-lookup
agent/software-canonical-lookup-request
collector/nvd-index
collector/nvd-cve
package-manager/maven
vendor/jenkins
canonical/jenkins
version/jenkins/1.0

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-45394?
CVE-2022-45394 is classified as a critical vulnerability due to its potential impact on sensitive build logs.
How do I fix CVE-2022-45394?
To fix CVE-2022-45394, upgrade to a version of the Jenkins Delete log Plugin that is newer than 1.0.
What causes CVE-2022-45394?
CVE-2022-45394 is caused by a missing permission check that allows users with Item/Read permission to delete build logs.
Which versions of Jenkins are affected by CVE-2022-45394?
Versions of the Jenkins Delete log Plugin prior to 1.0 are affected by CVE-2022-45394.
What can attackers do with CVE-2022-45394?
Attackers can exploit CVE-2022-45394 to delete build logs if they have Item/Read permissions.