CVE-2022-27211 json
CSRF vulnerability and missing permission checks in Jenkins kubernetes-cd Plugin allow capturing credentials
published 4y ago modified 4mo ago also GHSA-794j-hx96-4w3m , EUVD-2022-1357
- cvss
- 6.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.9%
- EPSS 0.9% chance of exploitation in 30 days, percentile 60%
- public exploits
- 0
- none known
Summary
A missing permission check in Jenkins Kubernetes Continuous Deploy Plugin 2.3.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.
Is CVE-2022-27211 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2y ago
Exploit prediction
0.92% chance of exploitation in the next 30 days, higher than 60% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 4.0 | AV:N/AC:L/Au:S/C:P/I:N/A:N |
| GitHub | 3.1 | 7.1 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.jenkins-ci.plugins:kubernetes-cd | <=2.3.1 |
no fix listed |
Affected products
- Jenkins project Jenkins Kubernetes Continuous Deploy Plugin
Classification
- Weakness
-
- CWE-862 Missing Authorization
References
-
jenkins.io
/security/advisory/2022-03-15/#SECURITY-2681
web, vendor-advisory
-
openwall.com
/lists/oss-security/2022/03/15/2
mailing-list, web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2022-27211
advisory
-
github.com
/jenkinsci/kubernetes-cd-plugin
package
Sources
- CVE List CVE-2022-27211
- GitHub Advisory GHSA-794j-hx96-4w3m
- NVD CVE-2022-27211
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.