dbcve.org
Kubernetes Continuous DeployApplication · Jenkins

CVE-2022-27209

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 enumerate credentials IDs of 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 Kubernetes Continuous Deploy Plugin for Jenkins versions 2.3.1 and earlier lacks proper permission checks on endpoints that expose credential IDs. Any authenticated user with basic Overall/Read permission can query these endpoints to enumerate the IDs of credentials stored in Jenkins, potentially aiding attackers in credential theft campaigns.

MitigationUpdate Jenkins Kubernetes Continuous Deploy Plugin to version 2.3.2 or later, which includes proper permission checks on credential enumeration endpoints.

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. Verify Kubernetes Continuous Deploy plugin is installed
    Navigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Kubernetes Continuous Deploy' plugin, or use the Jenkins CLI: java -jar jenkins-cli.jar list-plugins | grep -i kubernetes
    Affected if The plugin appears in the installed plugins list
  2. Determine installed plugin version
    In the Installed Plugins page, locate the Version column for Kubernetes Continuous Deploy plugin; alternatively, inspect the manifest file at $JENKINS_HOME/plugins/kubernetes-cd/WEB-INF/manifest.json
    Affected if Version is 2.3.1 or earlier (compare against affected range <= 2.3.1)
  3. Review user accounts with access to Jenkins
    Navigate to Manage Jenkins > Manage Users to see all user accounts; check Manage Jenkins > Configure Global Security to review authorization settings and permission matrices
    Affected if More than one user account exists with Overall/Read permission (any authenticated user can exploit this flaw)

Environment is affected if Kubernetes Continuous Deploy plugin version 2.3.1 or earlier is installed and multiple user accounts have Overall/Read permission, allowing low-privilege users to enumerate credential IDs.

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

Update Jenkins Kubernetes Continuous Deploy Plugin to version 2.3.2 or later, which includes proper permission checks on credential enumeration endpoints.

Recommended fix Moderate confidence

Latest available version of Kubernetes Continuous Deploy plugin (version > 2.3.1)

  1. Navigate to Manage Jenkins > Manage Plugins
  2. Locate the 'Kubernetes Continuous Deploy' plugin in the 'Installed' tab
  3. Check if an update is available for the Kubernetes Continuous Deploy plugin
  4. If an update is available, click 'Update now' to install the fixed version
  5. After updating, restart Jenkins or wait for the plugin to reload
  6. Verify the plugin has been updated to a version higher than 2.3.1

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

Fix this in Kubernetes Continuous Deploy Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-27209 — 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-27209 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