dbcve.org
Code Coverage ApiApplication · Jenkins

CVE-2021-21677

HIGH · 8.8 CVSS v3.1 Published 2021-08-31
Fix available
A fix is available. Upgrade to after 1.4.0 or later.
See remediation →
94/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
Jenkins Code Coverage API Plugin 1.4.0 and earlier does not apply Jenkins JEP-200 deserialization protection to Java objects it deserializes from disk, resulting in a remote code execution vulnerability.

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 Code Coverage API Plugin versions 1.4.0 and earlier deserializes Java objects from disk without applying JEP-200 deserialization protection, which is a core Jenkins security mechanism. This allows an attacker who can control or place malicious serialized objects in locations read by the plugin to achieve remote code execution on the Jenkins controller or agent.

MitigationUpgrade to a patched version of the Code Coverage API Plugin that applies JEP-200 deserialization filtering to all disk-loaded objects; alternatively, remove or disable the plugin until a fix is available.

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
Code Coverage ApiApplication
Affected:<= 1.4.0

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

CVSS:3.1/AV:N/AC:L/PR:L/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. Verify Code Coverage API Plugin is installed
    Navigate to Manage Jenkins > Manage Plugins > Installed tab, or run: jenkins-cli.jar who-am-i (if available), or inspect the Jenkins plugin directory at $JENKINS_HOME/plugins/ for a folder named 'code-coverage-api'
    Affected if The plugin folder exists in the plugins directory or is listed in Manage Plugins > Installed
  2. Determine the installed version of Code Coverage API Plugin
    In Jenkins UI, go to Manage Jenkins > Manage Plugins > Installed tab and locate Code Coverage API Plugin in the list to see its version number; alternatively, inspect the plugin's manifest file at $JENKINS_HOME/plugins/code-coverage-api/META-INF/MANIFEST.MF
    Affected if The version is 1.4.0 or any version lower than 1.4.0 (e.g., 1.3.0, 1.2.0, 1.1.0)
  3. Confirm the plugin is active and not disabled
    In Jenkins UI under Manage Plugins > Installed, verify that Code Coverage API Plugin shows as 'Enabled' or 'Active'; check $JENKINS_HOME/plugins/code-coverage-api/.disabled file does NOT exist
    Affected if The plugin is enabled and loaded by Jenkins at runtime (not uninstalled or marked as disabled)
  4. Check if coverage reports are being processed
    Inspect Jenkins job configurations for any pipelines or freestyle jobs that publish code coverage results using the Code Coverage API plugin; review job logs or the $JENKINS_HOME/jobs/*/builds/*/coverage*.xml files if any exist
    Affected if Jobs are configured to publish coverage results via this plugin, causing the plugin to deserialize coverage data files

You are affected if the Code Coverage API Plugin is installed at version 1.4.0 or earlier, is currently enabled, and the plugin processes or reads serialized coverage data files.

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

Upgrade to a patched version of the Code Coverage API Plugin that applies JEP-200 deserialization filtering to all disk-loaded objects; alternatively, remove or disable the plugin until a fix is available.

Recommended fix High confidence

Code Coverage API Plugin version 1.4.1 or later

  1. Navigate to Manage Jenkins > Manage Plugins
  2. Go to the 'Installed' tab
  3. Locate 'Code Coverage API' plugin in the list
  4. Check for updates or update the plugin directly
  5. Ensure the updated version is 1.4.1 or later
  6. Restart Jenkins if required to complete the update

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

Fix this in Code Coverage Api Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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