dbcve.org
Script SecurityApplication · Jenkins

CVE-2022-43401

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 various casts performed implicitly by the Groovy language runtime 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

Jenkins Script Security Plugin versions 1183.v774b_0b_0a_a_451 and earlier contain a sandbox bypass vulnerability where implicit type casts performed by the Groovy language runtime can be exploited by attackers with script execution permissions (including Pipeline users) to escape sandbox isolation and execute arbitrary code on the Jenkins controller JVM.

MitigationUpdate the Jenkins Script Security Plugin to the latest patched version. Review and audit any existing Pipeline scripts and sandboxed definitions for malicious content, as the CVSS 9.9 rating indicates active exploitation risk in exposed deployments.

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. Identify Script Security Plugin version
    Navigate to Manage Jenkins > Manage Plugins > Installed and locate the Script Security plugin in the list. Note the version number displayed in the Version column.
    Affected if The displayed version is 1183.v774b_0b_0a_a_451 or any version number that precedes it (earlier version numbers).
  2. Verify plugin is active
    Confirm the Script Security plugin shows as 'Enabled' or 'Active' in the plugin manager.
    Affected if The plugin is installed and active.
  3. Check for script execution permission assignments
    Review Jenkins authorization configuration at Manage Jenkins > Configure Global Security. Identify which users or groups have the 'Run Scripts' or 'Pipeline' permission, or are assigned to a role that includes script execution capabilities.
    Affected if Any user account or service account beyond administrators has script/Pipeline execution permissions enabled.
  4. Review Pipeline usage
    Inspect active Pipeline jobs and any shared libraries defined in your Jenkins instance to determine if Pipeline scripts are in use, which would exercise the sandbox.
    Affected if Pipeline jobs or shared libraries are defined and actively used.

If the Script Security Plugin version is 1183.v774b_0b_0a_a_451 or earlier AND any user has script execution or Pipeline permissions, the environment is vulnerable to sandbox escape.

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

Update the Jenkins Script Security Plugin to the latest patched version. Review and audit any existing Pipeline scripts and sandboxed definitions for malicious content, as the CVSS 9.9 rating indicates active exploitation risk in exposed deployments.

Recommended fix High confidence

Upgrade Script Security Plugin to version 1184.v88d_7b_1d0d_d5b or later (the first fixed release)

  1. 1. Identify the Jenkins instance running the vulnerable Script Security Plugin version <= 1183.v774b_0b_0a_a_451
  2. 2. Navigate to Manage Jenkins > Manage Plugins
  3. 3. Locate the Script Security plugin in the Installed tab
  4. 4. Check for available updates and upgrade to the latest version
  5. 5. Restart Jenkins or the Jenkins controller as required for the plugin update to take effect
  6. 6. Verify the upgrade was successful by confirming the new plugin version in the installed plugins list

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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