What is the severity of CVE-2022-30969?

CVE-2022-30969 is considered a critical severity vulnerability due to its potential to allow arbitrary code execution.

How do I fix CVE-2022-30969?

To fix CVE-2022-30969, update the Jenkins Autocomplete Parameter Plugin to version 1.1 or later.

Is CVE-2022-30969 exploitable by non-administrators?

No, CVE-2022-30969 requires the victim to be an administrator for exploitation.

What impact does CVE-2022-30969 have on Jenkins installations?

CVE-2022-30969 could lead to unauthorized actions in Jenkins environments, compromising security and stability.

Are there any known workarounds for CVE-2022-30969?

There are currently no specific workarounds for CVE-2022-30969 aside from updating to the patched version.

Vulnerability/
CVE-2022-30969

high

8.8

CWE

352

17/5/2022

3/8/2024

CVE-2022-30969: CSRF

First published: Tue May 17 2022(Updated: )

A cross-site request forgery (CSRF) vulnerability in Jenkins Autocomplete Parameter Plugin 1.1 and earlier allows attackers to execute arbitrary code without sandbox protection if the victim is an administrator.

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

Affected Software	Affected Version	How to fix
Jenkins Autocomplete Parameter	<=1.1

Never miss a vulnerability like this again

Reference Links

https://www.jenkins.io/security/advisory/2022-05-17/#SECURITY-2322

Frequently Asked Questions

What is the severity of CVE-2022-30969?
CVE-2022-30969 is considered a critical severity vulnerability due to its potential to allow arbitrary code execution.
How do I fix CVE-2022-30969?
To fix CVE-2022-30969, update the Jenkins Autocomplete Parameter Plugin to version 1.1 or later.
Is CVE-2022-30969 exploitable by non-administrators?
No, CVE-2022-30969 requires the victim to be an administrator for exploitation.
What impact does CVE-2022-30969 have on Jenkins installations?
CVE-2022-30969 could lead to unauthorized actions in Jenkins environments, compromising security and stability.
Are there any known workarounds for CVE-2022-30969?
There are currently no specific workarounds for CVE-2022-30969 aside from updating to the patched version.

collector/nvd-index
collector/nvd-api
agent/author
agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/references
agent/severity
agent/weakness
agent/tags
agent/description
agent/first-publish-date
agent/event
agent/source
vendor/jenkins
canonical/jenkins autocomplete parameter
version/jenkins autocomplete parameter/1.1

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-30969?
CVE-2022-30969 is considered a critical severity vulnerability due to its potential to allow arbitrary code execution.
How do I fix CVE-2022-30969?
To fix CVE-2022-30969, update the Jenkins Autocomplete Parameter Plugin to version 1.1 or later.
Is CVE-2022-30969 exploitable by non-administrators?
No, CVE-2022-30969 requires the victim to be an administrator for exploitation.
What impact does CVE-2022-30969 have on Jenkins installations?
CVE-2022-30969 could lead to unauthorized actions in Jenkins environments, compromising security and stability.
Are there any known workarounds for CVE-2022-30969?
There are currently no specific workarounds for CVE-2022-30969 aside from updating to the patched version.