dbcve.org
Kubernetes Continuous DeployApplication · Jenkins

CVE-2022-27211

MEDIUM · 6.5 CVSS v3.1 Published 2022-03-15
Fix available
A fix is available. Upgrade to after 2.3.1 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Jenkins Kubernetes Continuous Deploy Plugin 2.3.1 and earlier lacks a permission check before allowing connections to attacker-specified SSH servers using credential IDs. Attackers with only Overall/Read permission can exploit this to connect to arbitrary SSH servers using credentials obtained through another method, enabling credential capture.

MitigationUpgrade to a patched version of the Kubernetes Continuous Deploy Plugin that includes proper permission checks. Until patched, minimize user permissions and audit credential storage configurations.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Kubernetes Continuous DeployApplication
Affected:<= 2.3.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if Kubernetes Continuous Deploy plugin is installed
    Navigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab, or use the Jenkins CLI: java -jar jenkins-cli.jar list-plugins. Look for 'Kubernetes Continuous Deploy' in the plugin list.
    Affected if The plugin is listed and the version shown is 2.3.1 or earlier, or if no version is displayed but the plugin is present in an older Jenkins installation.
  2. Identify the installed plugin version
    In the Installed plugins tab, find the 'Kubernetes Continuous Deploy' entry and note the Version column. Alternatively, check the manifest file: $JENKINS_HOME/plugins/kubernetes-cd/META-INF/MANIFEST.MF
    Affected if The version is 2.3.1 or any version lower than that.
  3. Check for configured credentials in Jenkins
    Navigate to Jenkins > Credentials > System > Global credentials (or the specific domain where SSH credentials may be stored). Review whether any SSH username with private key or other credentials are defined.
    Affected if Any SSH or other credentials are stored in Jenkins that could be referenced by the plugin's credential ID parameter.
  4. Verify if users have Overall/Read permission
    Navigate to Jenkins > Manage Jenkins > Manage Users, then check Configure Global Security or matrix-based permissions. Look for whether 'Overall/Read' permission is granted to users other than administrators.
    Affected if Non-admin users have Overall/Read permission, which is required for the attacker to exploit this vulnerability.
  5. Check for Kubernetes deployment configurations using the plugin
    Look for job configurations or pipeline scripts that use the 'kubernetes-cd' plugin functionality, particularly any that reference kubectl with credential IDs or Kubernetes config files.
    Affected if Any Jenkins jobs or pipelines are configured to deploy to Kubernetes using the affected plugin.

The environment is affected if the Kubernetes Continuous Deploy plugin version 2.3.1 or earlier is installed, credentials are stored in Jenkins, and users with Overall/Read permission exist alongside deployment configurations using the plugin.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 2.3.1
Interim mitigation

Upgrade to a patched version of the Kubernetes Continuous Deploy Plugin that includes proper permission checks. Until patched, minimize user permissions and audit credential storage configurations.

Recommended fix High confidence

Kubernetes Continuous Deploy Plugin 2.3.2

  1. Navigate to Jenkins dashboard
  2. Go to Manage Jenkins > Manage Plugins
  3. Select the 'Installed' tab
  4. Locate 'Kubernetes Continuous Deploy' plugin
  5. If version is 2.3.1 or earlier, click 'Update now' to upgrade to version 2.3.2 or later
  6. Restart Jenkins if required to complete the upgrade
  7. Alternatively, download the latest version from the Jenkins plugin repository and manually upload via 'Advanced' tab > 'Upload Plugin'

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Kubernetes Continuous Deploy Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-27211 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-27211 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data