dbcve.org
Docker Build StepApplication · Jenkins

CVE-2024-2216

HIGH · 8.8 CVSS v3.1 Published 2024-03-06
Fix available
A fix is available. Upgrade to after 2.11 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
A missing permission check in an HTTP endpoint in Jenkins docker-build-step Plugin 2.11 and earlier allows attackers with Overall/Read permission to connect to an attacker-specified TCP or Unix socket URL, and to reconfigure the plugin using the provided connection test parameters, affecting future build step executions.

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-build-step Plugin versions 2.11 and earlier contains a missing permission check in an HTTP endpoint. Attackers with only Overall/Read permission (typically considered low-privilege) can exploit this to connect to attacker-specified TCP or Unix socket URLs and to modify plugin configuration via connection test parameters, persisting changes that affect subsequent build step executions.

MitigationUpgrade the docker-build-step plugin to version 2.12 or later, which addresses the missing permission check. If immediate upgrade is not feasible, restrict Overall/Read permission to only trusted users.

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 Build StepApplication
Affected:<= 2.11

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-build-step plugin is installed
    Navigate to Manage Jenkins > Manage Plugins > Installed and search for 'docker-build-step', or use the Jenkins CLI: java -jar jenkins-cli.jar -s http://localhost:8080 list-plugins docker-build-step
    Affected if The plugin is not found in the installed plugins list, meaning the plugin is not present and therefore not affected
  2. Determine the installed version of docker-build-step plugin
    In the Jenkins UI, go to Manage Jenkins > Manage Plugins > Installed and locate the Version column for docker-build-step; or query via API: curl -s http://localhost:8080/pluginManager/plugin/docker-build-step/api/json?pretty=true
    Affected if The displayed version number is 2.11 or lower (e.g., 2.11, 2.10, 2.9, etc.)
  3. Verify Overall/Read permission assignments
    Navigate to Manage Jenkins > Manage Users and review which users and groups have Overall/Read permission under Configure Global Security; check both matrix-based security and project-based authorization settings
    Affected if Any user or group with Overall/Read permission is considered low-privilege and could potentially exploit this vulnerability if the plugin version is <= 2.11
  4. Check for unauthorized connections or modified configuration
    Review the plugin configuration at Manage Jenkins > Configure System > Docker Build Step for any unexpected socket URLs, connection test parameters, or configuration changes you did not make
    Affected if The configuration contains socket URLs, connection parameters, or settings that were not intentionally configured by your administrators

A user is affected if the docker-build-step plugin is installed at version 2.11 or earlier AND any untrusted users have Overall/Read permission in the Jenkins environment.

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.11
Interim mitigation

Upgrade the docker-build-step plugin to version 2.12 or later, which addresses the missing permission check. If immediate upgrade is not feasible, restrict Overall/Read permission to only trusted users.

Recommended fix Moderate confidence

Latest available version of docker-build-step plugin (version greater than 2.11)

  1. Navigate to Jenkins Dashboard
  2. Go to Manage Jenkins > Manage Plugins
  3. Select the 'Updates' tab
  4. Find 'docker-build-step' plugin in the list
  5. Select the plugin and click 'Download now and install after restart'
  6. Wait for plugin update to complete
  7. Restart Jenkins if required
  8. Verify plugin version is updated to the latest available version
Caveat Review plugin release notes for any configuration or feature changes between versions

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

Fix this in Docker Build Step 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-2024-2216 — 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-2024-2216 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