What is the severity of CVE-2022-28147?

CVE-2022-28147 is classified as a medium-severity vulnerability due to the potential for unauthorized file path enumeration.

How do I fix CVE-2022-28147?

To fix CVE-2022-28147, upgrade the Jenkins Continuous Integration with Toad Edge Plugin to version 2.4 or later.

Who is affected by CVE-2022-28147?

Jenkins Continuous Integration with Toad Edge Plugin versions 2.3 and earlier are affected by CVE-2022-28147.

What type of attack is possible due to CVE-2022-28147?

CVE-2022-28147 allows attackers to check for the existence of specific file paths on the Jenkins controller.

What permissions are required to exploit CVE-2022-28147?

Attackers only need Overall/Read permission on Jenkins to exploit CVE-2022-28147.

Vulnerability/
CVE-2022-28147

medium

4.3

CWE

862

29/3/2022

3/8/2024

CVE-2022-28147

First published: Tue Mar 29 2022(Updated: )

A missing permission check in Jenkins Continuous Integration with Toad Edge Plugin 2.3 and earlier allows attackers with Overall/Read permission to check for the existence of an attacker-specified file path on the Jenkins controller file system.

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

Affected Software	Affected Version	How to fix
Jenkins Continuous Integration With Toad Edge	<=2.3

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2022-28147?
CVE-2022-28147 is classified as a medium-severity vulnerability due to the potential for unauthorized file path enumeration.
How do I fix CVE-2022-28147?
To fix CVE-2022-28147, upgrade the Jenkins Continuous Integration with Toad Edge Plugin to version 2.4 or later.
Who is affected by CVE-2022-28147?
Jenkins Continuous Integration with Toad Edge Plugin versions 2.3 and earlier are affected by CVE-2022-28147.
What type of attack is possible due to CVE-2022-28147?
CVE-2022-28147 allows attackers to check for the existence of specific file paths on the Jenkins controller.
What permissions are required to exploit CVE-2022-28147?
Attackers only need Overall/Read permission on Jenkins to exploit CVE-2022-28147.

collector/nvd-index
collector/nvd-api
agent/references
agent/author
agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/weakness
agent/last-modified-date
agent/severity
agent/tags
agent/first-publish-date
agent/description
agent/event
agent/source
vendor/jenkins
canonical/jenkins continuous integration with toad edge
version/jenkins continuous integration with toad edge/2.3

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-28147?
CVE-2022-28147 is classified as a medium-severity vulnerability due to the potential for unauthorized file path enumeration.
How do I fix CVE-2022-28147?
To fix CVE-2022-28147, upgrade the Jenkins Continuous Integration with Toad Edge Plugin to version 2.4 or later.
Who is affected by CVE-2022-28147?
Jenkins Continuous Integration with Toad Edge Plugin versions 2.3 and earlier are affected by CVE-2022-28147.
What type of attack is possible due to CVE-2022-28147?
CVE-2022-28147 allows attackers to check for the existence of specific file paths on the Jenkins controller.
What permissions are required to exploit CVE-2022-28147?
Attackers only need Overall/Read permission on Jenkins to exploit CVE-2022-28147.