dbcve.org
Installation Manager ToolApplication · Jenkins

CVE-2020-2320

CRITICAL · 9.8 CVSS v3.1 Published 2020-12-03
Fix available
A fix is available. Upgrade to after 2.1.3 or later.
See remediation →
100/100
Remediation priority · Urgent
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 Plugin Installation Manager Tool 2.1.3 and earlier does not verify plugin downloads.

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 Jenkins Plugin Installation Manager Tool versions 2.1.3 and earlier lacks integrity verification (checksums or signatures) when downloading plugins, allowing man-in-the-middle attackers to serve malicious or tampered plugins.

MitigationUpgrade to a version that implements plugin download verification, or use network-level controls to ensure plugins are downloaded only from trusted sources.

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
Installation Manager ToolApplication
Affected:<= 2.1.3

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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 the Jenkins Plugin Installation Manager Tool installation
    Locate the plugin installation manager tool by searching for files named 'install-plugins.sh', 'jenkins-plugin-cli', or the 'pluginInstallationManager' artifact in your environment. Check common locations like /usr/local/bin, /opt, or within Jenkins home directories.
    Affected if The tool is present on the system and used for downloading Jenkins plugins.
  2. Determine the installed version
    Run the tool with a version flag such as 'java -jar pluginInstallationManager.jar --version' or 'jenkins-plugin-cli --version', or inspect the filename or manifest of the JAR file itself.
    Affected if The reported version is 2.1.3 or earlier, or the version cannot be determined (indicating an unpatched older release).
  3. Verify plugin download behavior
    Review any scripts, pipelines, or CI/CD configurations that invoke the installation manager tool to download plugins. Check the command arguments used, such as 'jenkins-plugin-cli -p plugin1,plugin2' or similar patterns.
    Affected if The tool is being executed to download plugins from remote update centers or external URLs without additional integrity verification.
  4. Inspect for integrity verification configuration
    Examine the tool's configuration files, command-line arguments, or any wrapper scripts for the presence of checksum validation, signature verification, or hash comparison options. Look for flags like '-checksum', '-verify', or similar integrity-related parameters.
    Affected if No integrity verification mechanism (checksums, signatures, or hash validation) is configured or passed to the tool when downloading plugins.

You are affected if the Jenkins Plugin Installation Manager Tool version 2.1.3 or earlier is in use and plugins are downloaded from remote sources without any integrity verification (checksums or signatures) in place.

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 2.1.3
Interim mitigation

Upgrade to a version that implements plugin download verification, or use network-level controls to ensure plugins are downloaded only from trusted sources.

Recommended fix Moderate confidence

Latest version after 2.1.3 (check Jenkins plugin repository for current release)

  1. 1. Identify the current version of Jenkins Plugin Installation Manager Tool in use
  2. 2. Check Jenkins Plugin Installation Manager Tool releases for versions after 2.1.3
  3. 3. Upgrade to the latest stable version available that includes the integrity verification fix
  4. 4. Verify the upgrade was successful by checking the installed version

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

Fix this in Installation Manager Tool Scoped from the published advisory
  • Consultation6.0 h
  • Implementation20.0 h
  • Testing12.0 h
  • Review / QA6.0 h
44.0 hours of engineering $7,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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