CVE-2022-30959
First published: Tue May 17 2022(Updated: )
A missing permission check in Jenkins SSH Plugin 2.6.1 and earlier allows attackers with Overall/Read permission to connect to an attacker-specified SSH server using attacker-specified credentials IDs obtained through another method, capturing credentials stored in Jenkins.
Credit: jenkinsci-cert@googlegroups.com jenkinsci-cert@googlegroups.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Jenkins Ssh | <=2.6.1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Frequently Asked Questions
What is the severity of CVE-2022-30959?
CVE-2022-30959 is classified as a high severity vulnerability due to its ability to expose sensitive credentials.
How do I fix CVE-2022-30959?
To fix CVE-2022-30959, upgrade Jenkins SSH Plugin to version 2.6.2 or later.
Who is affected by CVE-2022-30959?
Any Jenkins instance running the SSH Plugin version 2.6.1 or earlier is vulnerable to CVE-2022-30959.
What kind of attack is possible with CVE-2022-30959?
CVE-2022-30959 allows attackers to connect to arbitrary SSH servers and capture Jenkins stored credentials.
What permissions are required to exploit CVE-2022-30959?
Exploitation of CVE-2022-30959 requires the attacker to have Overall/Read permission in Jenkins.
- collector/nvd-index
- collector/nvd-api
- agent/author
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/severity
- agent/last-modified-date
- agent/references
- agent/weakness
- agent/description
- agent/event
- agent/first-publish-date
- agent/tags
- agent/source
- vendor/jenkins
- canonical/jenkins ssh
- version/jenkins ssh/2.6.1