Script SecurityApplication · Jenkins
CVE-2022-43403
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 · uneditedA sandbox bypass vulnerability involving casting an array-like value to an array type 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 confidenceA sandbox bypass vulnerability in Jenkins Script Security Plugin 1183.v774b_0b_0a_a_451 and earlier allows attackers with script execution permissions to bypass sandbox restrictions by casting array-like values to array types, enabling arbitrary code execution on the Jenkins controller.
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
<= 1183.v774b_0b_0a_a_451CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Script Security Plugin versionNavigate to Manage Jenkins > Manage Plugins > Installed tab and locate Script Security Plugin, or inspect the plugin manifest file in JENKINS_HOME/plugins/script-security/WEB-INF/MANIFEST.MFAffected if Version is 1183.v774b_0b_0a_a_451 or earlier
-
Confirm script execution permissions existReview Jenkins authorization configuration (Manage Jenkins > Configure Global Security > Authorization) and check if any users or groups have Overall/Run Scripts or Job/Build permissions grantedAffected if Any user or service account has script execution permissions enabled
-
Check for Groovy sandbox usageInspect pipeline jobs, Jenkinsfiles, or scripted build steps to determine if Groovy scripts are configured to run with sandbox enabled (script blocks using @Grab or sandbox() method)Affected if Pipeline or freestyle jobs use sandboxed Groovy script execution
If the Script Security Plugin version is 1183 or earlier and any user has script execution permissions in a sandboxed environment, the vulnerability is present.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpdate Jenkins Script Security Plugin to version 1184.v774b_0b_0a_451 or later to patch the sandbox bypass vulnerability.
Script Security Plugin version 1185.vf68b_3994b_8 or later
- Log in to Jenkins as an administrator
- Navigate to Manage Jenkins > Manage Plugins
- Click on the Updates tab
- Locate 'Script Security Plugin' in the list
- Select the checkbox next to Script Security Plugin
- Click 'Download now and install after restart'
- Wait for the plugin to download and install
- Restart Jenkins (or click 'Restart Jenkins when no jobs are running')
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
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,904.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-43403 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-43403 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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