Cyber Resilience

CVE-2024-2215

CSRF in Jenkins Docker-Build-Step ≤ 2.11

CSRF
Published
06 March 2024
Modified
17 June 2026
Patch / advisory
View advisory
CVSS Score v3.1 6.1
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:L/A:L
EPSS Score 0.0041 34th percentile
Risk Priority 46 floored blend · peak EPSS

Summary

CVE-2024-2215 is a medium-severity CSRF (CWE-352) vulnerability in Jenkins Docker-Build-Step. Its CVSS base score is 6.1 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 34th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and SC-23 (Session Authenticity) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A01:2025 Broken Access Control

EU & UK References

Vulnerability Data

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…

more

executions.

CWE(s)
CWE-352

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-50766Same vendor: Jenkins
CVE-2023-32995Same vendor: Jenkins
CVE-2023-50768Same vendor: Jenkins
CVE-2023-37954Same vendor: Jenkins
CVE-2023-32989Same vendor: Jenkins
CVE-2023-37952Same vendor: Jenkins
CVE-2023-37962Same vendor: Jenkins
CVE-2023-30525Same vendor: Jenkins
CVE-2023-24437Same vendor: Jenkins
CVE-2023-35148Same vendor: Jenkins

Affected Assets

jenkins
docker-build-step
≤ 2.11

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V3.3.2
  • V3.5.1
  • V10.2.1

Mitigating Controls (NIST 800-53 r5) AI

AC-3 Access Enforcement partial match

Access enforcement requires verifying that state-changing requests originate from the authenticated user rather than a forged cross-site source.

SC-23 Session Authenticity partial match

Protecting session authenticity prevents attackers from replaying or forging authenticated requests via the victim's browser.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require anti-CSRF controls such as tokens or SameSite attributes.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.23 Web filtering partial match
mitigates

By denying access to phishing or malicious sites, the control lowers the likelihood that a user will be tricked into submitting a forged request that performs an unintended action on another site.

A.5.7 Threat intelligence none match
none

Contextual intelligence about emerging CSRF toolkits can be translated into updated anti-CSRF token or same-site policy configurations across applications.

References