What is the severity of CVE-2022-34187?

The severity of CVE-2022-34187 is rated as high due to the potential for stored cross-site scripting (XSS) attacks.

Who is affected by CVE-2022-34187?

CVE-2022-34187 affects users of Jenkins Filesystem List Parameter Plugin versions 0.0.7 and earlier.

How do I fix CVE-2022-34187?

To fix CVE-2022-34187, upgrade to Jenkins Filesystem List Parameter Plugin version 0.0.8 or later.

What are the consequences of exploiting CVE-2022-34187?

Exploiting CVE-2022-34187 can allow attackers with Item/Configure permission to execute malicious scripts in the context of other users.

Is there a workaround for CVE-2022-34187 if I can't upgrade?

There are no recommended workarounds for CVE-2022-34187; upgrading to a secure version is the best solution.

Vulnerability/
CVE-2022-34187

medium

5.4

CWE

22/6/2022

3/8/2024

CVE-2022-34187: XSS

First published: Wed Jun 22 2022(Updated: )

Jenkins Filesystem List Parameter Plugin 0.0.7 and earlier does not escape the name and description of File system objects list parameters on views displaying parameters, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers with Item/Configure permission.

Credit: jenkinsci-cert@googlegroups.com

Affected Software	Affected Version	How to fix
Jenkins Filesystem List Parameter Plugin	<=0.0.7

Never miss a vulnerability like this again

Reference Links

https://www.jenkins.io/security/advisory/2022-06-22/#SECURITY-2784

Frequently Asked Questions

What is the severity of CVE-2022-34187?
The severity of CVE-2022-34187 is rated as high due to the potential for stored cross-site scripting (XSS) attacks.
Who is affected by CVE-2022-34187?
CVE-2022-34187 affects users of Jenkins Filesystem List Parameter Plugin versions 0.0.7 and earlier.
How do I fix CVE-2022-34187?
To fix CVE-2022-34187, upgrade to Jenkins Filesystem List Parameter Plugin version 0.0.8 or later.
What are the consequences of exploiting CVE-2022-34187?
Exploiting CVE-2022-34187 can allow attackers with Item/Configure permission to execute malicious scripts in the context of other users.
Is there a workaround for CVE-2022-34187 if I can't upgrade?
There are no recommended workarounds for CVE-2022-34187; upgrading to a secure version is the best solution.

agent/author
agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/severity
agent/last-modified-date
agent/references
agent/weakness
agent/first-publish-date
agent/description
agent/event
agent/source
agent/tags
collector/nvd-api
agent/software-canonical-lookup-request
collector/nvd-index
vendor/jenkins
canonical/jenkins filesystem list parameter plugin
version/jenkins filesystem list parameter plugin/0.0.7

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-34187?
The severity of CVE-2022-34187 is rated as high due to the potential for stored cross-site scripting (XSS) attacks.
Who is affected by CVE-2022-34187?
CVE-2022-34187 affects users of Jenkins Filesystem List Parameter Plugin versions 0.0.7 and earlier.
How do I fix CVE-2022-34187?
To fix CVE-2022-34187, upgrade to Jenkins Filesystem List Parameter Plugin version 0.0.8 or later.
What are the consequences of exploiting CVE-2022-34187?
Exploiting CVE-2022-34187 can allow attackers with Item/Configure permission to execute malicious scripts in the context of other users.
Is there a workaround for CVE-2022-34187 if I can't upgrade?
There are no recommended workarounds for CVE-2022-34187; upgrading to a secure version is the best solution.