dbcve.org
Script SecurityApplication · Jenkins

CVE-2022-45379

HIGH · 7.5 CVSS v3.1 Published 2022-11-15
Fix available
A fix is available. Upgrade to 1190.v65867a_a_47126 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
Jenkins Script Security Plugin 1189.vb_a_b_7c8fd5fde and earlier stores whole-script approvals as the SHA-1 hash of the script, making it vulnerable to collision attacks.

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 1189.vb_a_b_7c8fd5fde and earlier stores whole-script approvals using SHA-1 hashing of the script content. SHA-1 is cryptographically weak against collision attacks, allowing an attacker to craft a malicious script that produces the same hash as an approved script, thereby bypassing script approval controls.

MitigationUpgrade Jenkins Script Security Plugin to a version newer than 1189.vb_a_b_7c8fd5fde. Alternatively, review and re-approve critical scripts using a more secure hash mechanism once the patch is applied.

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:< 1190.v65867a_a_47126

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 the Script Security Plugin version
    In the Jenkins web UI, go to Manage Jenkins > Manage Plugins > Installed tab, locate 'Script Security Plugin' and check the Version column. Alternatively, check the jenkins/plugins/script-security folder or the plugin manifest file.
    Affected if The installed version is 1189.vb_a_b_7c8fd5fde or earlier (any version below 1190.v65867a_a_47126).
  2. Determine if script approvals are in use
    Navigate to Manage Jenkins > In-process Script Approval, or check the script approval configuration file in the Jenkins home directory if accessible.
    Affected if There are approved scripts listed, meaning the script approval feature has been used.
  3. Verify SHA-1 hashing is in use for approvals
    Inspect the approved scripts storage mechanism - look at how approved script hashes are stored in the Script Security configuration or database. The approval system uses SHA-1 by default in affected versions.
    Affected if Approved scripts are stored with SHA-1 hashes (the vulnerability requires the SHA-1 hash mechanism to be used for script approval).

A user is affected if they have Script Security Plugin version 1189.vb_a_b_7c8fd5fde or earlier AND have any approved scripts, because the SHA-1 hashing used for approvals can be bypassed via collision attacks.

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 1190.v65867a_a_47126 or later
Fixed in 1190.v65867a_a_47126
Interim mitigation

Upgrade Jenkins Script Security Plugin to a version newer than 1189.vb_a_b_7c8fd5fde. Alternatively, review and re-approve critical scripts using a more secure hash mechanism once the patch is applied.

Recommended fix High confidence

1190.v65867a_a_47126

  1. Back up your Jenkins configuration and plugin data before updating
  2. Navigate to Manage Jenkins > Manage Plugins > Available tab
  3. Locate the Script Security plugin in the plugin list
  4. Update the Script Security plugin to version 1190.v65867a_a_47126 or later
  5. Restart Jenkins to apply the plugin update
  6. Verify the plugin has been updated to the correct version under Manage Plugins > Installed

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
  • Testing4.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,360
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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