dbcve.org
Docker CommonsApplication · Jenkins

CVE-2022-20617

HIGH · 8.8 CVSS v3.1 Published 2022-01-12
Fix available
A fix is available. Upgrade to after 1.17 or later.
See remediation →
94/100
Remediation priority · Urgent
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
Jenkins Docker Commons Plugin 1.17 and earlier does not sanitize the name of an image or a tag, resulting in an OS command execution vulnerability exploitable by attackers with Item/Configure permission or able to control the contents of a previously configured job's SCM repository.

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 Docker Commons Plugin 1.17 and earlier fails to sanitize image names and tags before passing them to OS command execution, allowing authenticated attackers with Item/Configure permission or SCM contributors to inject arbitrary OS commands through specially crafted image names or tags.

MitigationUpgrade to Jenkins Docker Commons Plugin version 1.18 or later. Until then, restrict Item/Configure permissions to trusted users only and audit jobs using Docker functionality.

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
Docker CommonsApplication
Affected:<= 1.17

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
High
Availability
High

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

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 Docker Commons Plugin is installed
    Navigate to Manage Jenkins > Manage Plugins > Installed tab, or use the Jenkins CLI to list plugins and search for docker-commons
    Affected if The Docker Commons Plugin is not installed
  2. Verify the installed version
    In the Installed plugins tab, locate the Docker Commons Plugin entry and note the version; compare your version against the affected range (1.17 and earlier)
    Affected if Version is 1.17 or earlier
  3. Identify jobs using Docker image names or tags
    Search job configurations for Docker-related fields such as docker-image, image name, or tag parameters; review $JENKINS_HOME/jobs/ for config.xml files containing docker-related elements, or use the Jenkins UI to inspect job configurations
    Affected if Jobs or pipelines reference Docker image names or tags that could accept user input
  4. Audit Item/Configure permission assignments
    Review who has Item/Configure permission on jobs that use Docker functionality; check Manage Jenkins > Manage and Assign Roles or job-level security settings for users or groups with configure permissions
    Affected if Users with Item/Configure permission on Docker-using jobs are untrusted or external contributors

You are affected if the Docker Commons Plugin version is 1.17 or earlier AND jobs using Docker image names/tags exist where untrusted users have Item/Configure permission.

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 1.17
Interim mitigation

Upgrade to Jenkins Docker Commons Plugin version 1.18 or later. Until then, restrict Item/Configure permissions to trusted users only and audit jobs using Docker functionality.

Recommended fix Moderate confidence

Docker Commons Plugin version 1.18 or later

  1. Navigate to the Jenkins dashboard
  2. Go to 'Manage Jenkins' > 'Manage Plugins'
  3. Select the 'Installed' tab
  4. Locate the 'Docker Commons' plugin in the list
  5. If an update is available, click 'Update' to upgrade to the fixed version
  6. Restart Jenkins if required to complete the installation

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

Fix this in Docker Commons Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
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,392.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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