dbcve.org
Script SecurityApplication · Jenkins

CVE-2022-43404

CRITICAL · 9.9 CVSS v3.1 Published 2022-10-19
Fix available
A fix is available. Upgrade to after 1183.v774b_0b_0a_a_451 or later.
See remediation →
100/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 sandbox bypass vulnerability involving crafted constructor bodies and calls to sandbox-generated synthetic constructors in Jenkins Script Security Plugin 1183.v774b_0b_0a_a_451 and earlier allows 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.

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 vulnerability allows attackers with permission to run sandboxed scripts (including Pipelines) to bypass the sandbox protection by crafting malicious constructor bodies that call sandbox-generated synthetic constructors, enabling arbitrary code execution on the Jenkins controller JVM.

MitigationUpgrade Jenkins Script Security Plugin to version 1184.v5a_4f4a_03d0 or later to remediate this sandbox bypass vulnerability.

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
Script SecurityApplication
Affected:<= 1183.v774b_0b_0a_a_451

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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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. Locate the Jenkins Script Security Plugin version
    Navigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Script Security', or use the Jenkins CLI: java -jar jenkins-cli.jar list-plugins | grep -i 'script security'
    Affected if The plugin is installed and its version is 1183.v774b_0b_0a_a_451 or lower (any version <= 1183.v774b_0b_0a_a_451)
  2. Verify the plugin version number
    In the plugin manager UI, the version is displayed alongside the plugin name. If using CLI, the version appears in the output after the plugin name.
    Affected if The displayed version is 1183.v774b_0b_0a_a_451 or any version below it (e.g., 1182.vb_0a_3e0b_7a_4, 1180.v5a_4f4a_03d0, etc.)
  3. Confirm Pipeline or sandboxed script usage exists
    Check for Pipeline jobs (Jenkinsfile-based or declarative) or any jobs using the 'Pipeline' job type, as these execute sandboxed Groovy scripts by default.
    Affected if Pipelines or any sandboxed script executions are configured or have run on this Jenkins instance
  4. Check for users with script execution permissions
    Review permissions at Manage Jenkins > Manage Users and in Configure Global Security to identify who has Job/Create, Job/Build, or Pipeline permissions (any permission that allows running Pipeline scripts).
    Affected if Any user or group has permission to create or run Pipeline jobs or other sandboxed scripts

You are affected if the Script Security Plugin is installed at version 1183.v774b_0b_0a_a_451 or lower AND your Jenkins instance has Pipeline jobs or users with permission to run sandboxed scripts.

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 1183.v774b_0b_0a_a_451
Interim mitigation

Upgrade Jenkins Script Security Plugin to version 1184.v5a_4f4a_03d0 or later to remediate this sandbox bypass vulnerability.

Recommended fix Moderate confidence

Script Security Plugin 1184.v88d63574b_6d1 or later

  1. 1. Navigate to Manage Jenkins > Manage Plugins
  2. 2. Go to the 'Installed' tab
  3. 3. Search for 'Script Security' plugin
  4. 4. If update available, select the plugin and click 'Update'
  5. 5. After update completes, restart Jenkins controller to apply changes
  6. 6. Alternatively, download the latest .hpi file from the Jenkins plugin repository and install via 'Advanced' > 'Upload Plugin'

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

Fix this in Script Security Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
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,936.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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