Vulnerability in org.jenkins-ci.plugins:script-security (CVE-2024-34145)
Summary
Vulnerability in org.jenkins-ci.plugins:script-security (CVE-2024-34145). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 1336.vf33a or later.
Original description
The description as published by the source.
Jenkins Script Security Plugin provides a sandbox feature that allows low privileged users to define scripts, including Pipelines, that are generally safe to execute. Calls to code defined inside a sandboxed script are intercepted, and various allowlists are checked to determine whether the call is to be allowed.
Multiple sandbox bypass vulnerabilities exist in Script Security Plugin 1335.vf07d9ce377a_e and earlier:
-
Crafted constructor bodies that invoke other constructors can be used to construct any subclassable type via implicit casts.
-
Sandbox-defined Groovy classes that shadow specific non-sandbox-defined classes can be used to construct any subclassable type.
These vulnerabilities allow attackers with permission to define and run sandboxed scripts, including Pipelines, to bypass the sandbox protection and execute arbitrary code in the context of the Jenkins controller JVM.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2024-34145 has been found in org.jenkins-ci.plugins:script-security.
Successful exploitation can lead to full system takeover.
What to do: upgrade org.jenkins-ci.plugins:script-security to 1336.vf33a or later.
If unsure, ask your IT team or search "org.jenkins-ci.plugins:script-security CVE-2024-34145" on the vendor's site.
CVE-2024-34145 (org.jenkins-ci.plugins:script-security) — CWE-290
Attack vector: remote (network-reachable) / no user interaction
Patched: 1336.vf33a — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-290) exists in org.jenkins-ci.plugins:script-security.
Check the vendor advisory for the affected versions of org.jenkins-ci.plugins:script-security.
Severity: ?. Successful exploitation can lead to full system takeover.
Update to 1336.vf33a.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで org.jenkins-ci.plugins:script-security を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade org.jenkins-ci.plugins:script-security to 1336.vf33aステージング環境で 1336.vf33a に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- web jenkins.io
- web openwall.com