dbcve.org
Docker Build StepApplication · Jenkins

CVE-2024-2215

MEDIUM · 6.1 CVSS v3.1 Published 2024-03-06
Fix available
A fix is available. Upgrade to after 2.11 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 cross-site request forgery (CSRF) vulnerability in Jenkins docker-build-step Plugin 2.11 and earlier allows attackers 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 · moderate confidence

A CSRF vulnerability in Jenkins docker-build-step Plugin version 2.11 and earlier allows authenticated users to be tricked into making requests that connect to attacker-specified TCP or Unix socket URLs and reconfigure the plugin with malicious connection test parameters. These attacker-controlled configurations persist and affect future build step executions.

MitigationUpgrade the docker-build-step plugin to a version newer than 2.11. Prior to upgrading, back up Jenkins configuration; after upgrade, test that build steps function correctly with expected socket 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
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
None
User interaction
Required
Scope
Changed
Confidentiality
None
Integrity
Low
Availability
Low

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

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 if docker-build-step plugin is installed
    Navigate to Manage Jenkins > Manage Plugins > Installed tab, or use: jenkins-cli or check $JENKINS_HOME/plugins/ for docker-build-step directory
    Affected if The plugin is present in the plugin list or filesystem
  2. Determine installed plugin version
    In the Installed Plugins page, find docker-build-step and note the Version column; or check the manifest file: $JENKINS_HOME/plugins/docker-build-step/META-INF/MANIFEST.MF for the Implementation-Version
    Affected if Version is 2.11 or lower (e.g., 2.11, 2.10, 2.9, etc.)
  3. Identify persisted plugin configurations
    Navigate to Manage Jenkins > Configure System and look for the Docker Build Step configuration section, or check $JENKINS_HOME/config.xml for <dockerBuildStep> entries
    Affected if There are socket URL configurations present that may have been injected via CSRF
  4. Review recent build logs for unexpected socket connections
    Examine recent build logs that use the Docker Build Step plugin, looking for connections to unexpected or external TCP/Unix socket paths
    Affected if Build logs show connections to unfamiliar or attacker-controlled socket URLs

If the docker-build-step plugin is installed at version 2.11 or earlier, the environment is affected by this CSRF vulnerability and may have malicious socket configurations persisted.

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 a version newer than 2.11. Prior to upgrading, back up Jenkins configuration; after upgrade, test that build steps function correctly with expected socket configurations.

Recommended fix Moderate confidence

docker-build-step plugin version > 2.11 (check Jenkins plugin repository for latest available version)

  1. 1. Navigate to the Jenkins dashboard
  2. 2. Go to Manage Jenkins > Manage Plugins
  3. 3. Select the 'Installed' tab
  4. 4. Find the 'docker-build-step' plugin in the list
  5. 5. If an update is available, click 'Update' or upgrade to the latest version
  6. 6. Restart Jenkins to apply the changes

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

Fix this in Docker Build Step Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,540
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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