What is the severity of CVE-2022-25199?

CVE-2022-25199 is considered a medium severity vulnerability due to the potential for unauthorized SSH connections.

How do I fix CVE-2022-25199?

To fix CVE-2022-25199, upgrade the Jenkins SCP Publisher Plugin to version 1.9 or later.

Who is affected by CVE-2022-25199?

CVE-2022-25199 affects users of Jenkins SCP Publisher Plugin versions 1.8 and earlier.

What type of attacks can exploit CVE-2022-25199?

CVE-2022-25199 can be exploited by attackers to connect to an arbitrary SSH server using credentials of their choosing.

What should I do if I cannot upgrade to fix CVE-2022-25199?

If upgrading is not possible, consider restricting access to users with Overall/Read permissions until a patch is applied for CVE-2022-25199.

Vulnerability/
CVE-2022-25199

high

8.8

CWE

862 352

15/2/2022

16/2/2022

3/8/2024

CVE-2022-25199: CSRF

First published: Tue Feb 15 2022(Updated: )

A missing permission check in Jenkins SCP publisher Plugin 1.8 and earlier allows attackers with Overall/Read permission to connect to an attacker-specified SSH server using attacker-specified credentials.

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

Affected Software	Affected Version	How to fix
Jenkins Scp Publisher	<=1.8
maven/org.jenkins-ci.plugins:scp	<=1.8

Remedy

https://www.jenkins.io/security/advisory/2022-02-15/#SECURITY-2323

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2022-25199?
CVE-2022-25199 is considered a medium severity vulnerability due to the potential for unauthorized SSH connections.
How do I fix CVE-2022-25199?
To fix CVE-2022-25199, upgrade the Jenkins SCP Publisher Plugin to version 1.9 or later.
Who is affected by CVE-2022-25199?
CVE-2022-25199 affects users of Jenkins SCP Publisher Plugin versions 1.8 and earlier.
What type of attacks can exploit CVE-2022-25199?
CVE-2022-25199 can be exploited by attackers to connect to an arbitrary SSH server using credentials of their choosing.
What should I do if I cannot upgrade to fix CVE-2022-25199?
If upgrading is not possible, consider restricting access to users with Overall/Read permissions until a patch is applied for CVE-2022-25199.

collector/nvd-index
collector/github-advisory-latest
alias/GHSA-vj3j-8m6x-mjq6
alias/CVE-2022-25199
collector/github-advisory
collector/nvd-api
agent/author
agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/remedy
agent/last-modified-date
agent/severity
agent/weakness
agent/references
agent/description
agent/event
agent/first-publish-date
agent/trending
agent/tags
agent/source
vendor/jenkins
canonical/jenkins scp publisher
version/jenkins scp publisher/1.8
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-25199?
CVE-2022-25199 is considered a medium severity vulnerability due to the potential for unauthorized SSH connections.
How do I fix CVE-2022-25199?
To fix CVE-2022-25199, upgrade the Jenkins SCP Publisher Plugin to version 1.9 or later.
Who is affected by CVE-2022-25199?
CVE-2022-25199 affects users of Jenkins SCP Publisher Plugin versions 1.8 and earlier.
What type of attacks can exploit CVE-2022-25199?
CVE-2022-25199 can be exploited by attackers to connect to an arbitrary SSH server using credentials of their choosing.
What should I do if I cannot upgrade to fix CVE-2022-25199?
If upgrading is not possible, consider restricting access to users with Overall/Read permissions until a patch is applied for CVE-2022-25199.