# CVE-2024-2215: Jenkins docker-build-step Plugin Cross-Site Request Forgery vulnerability

> Attackers can exploit CSRF to reconfigure the Jenkins docker-build-step plugin, altering connection settings for future builds.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 6 Mar 2024
- **Updated:** 13 Feb 2025
- **Also known as:** GHSA-64c5-r2h5-c2fg

## What is CVE-2024-2215?

CVE-2024-2215 is a medium-severity vulnerability in Jenkins docker-build-step Plugin, published on 6 Mar 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2024-2215?

2 open source packages ship an affected version, including org.jenkins-ci.plugins:docker-build-step. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.plugins:docker-build-step` | Maven | All versions to 2.11 | None |
| `org.jenkins-ci.plugins:docker-build-step` | Maven | All versions to 2.11 | None |

Products: Jenkins Docker-Build-Step.

## How do I fix CVE-2024-2215?

No fix has been published for CVE-2024-2215 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-2215 being exploited?

There is no known exploitation of CVE-2024-2215 in the wild and no public exploit code.

## Other vulnerabilities in Jenkins docker-build-step Plugin

- [CVE-2024-2216](https://insights.sbomify.com/CVE-2024-2216/): Jenkins docker-build-step Plugin missing permission check (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-2215 and fix it if it is affected.

What it is: CVE-2024-2215 is a medium-severity vulnerability in Jenkins docker-build-step Plugin, published on 6 Mar 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-2215 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.plugins:docker-build-step (Maven): affected all versions up to 2.11; no fix listed
- org.jenkins-ci.plugins:docker-build-step (Maven): affected all versions up to 2.11; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-2215/ (Markdown: https://insights.sbomify.com/CVE-2024-2215/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-2215
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-2215
- OSV: https://osv.dev/vulnerability/CVE-2024-2215

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-2215/
Summaries are generated and may contain mistakes; the official description above is the record.