dbcve.org
Echarts ApiApplication · Jenkins

CVE-2020-2194

MEDIUM · 5.4 CVSS v3.1 Published 2020-06-03
Fix available
A fix is available. Upgrade to after 4.7.0-3 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 ECharts API Plugin 4.7.0-3 and earlier does not escape the display name of the builds in the trend chart, resulting in a stored cross-site scripting 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 ECharts API Plugin versions 4.7.0-3 and earlier fails to properly sanitize build display names rendered in the trend chart, allowing stored malicious scripts to be executed when users view the affected chart.

MitigationUpgrade the Jenkins ECharts API Plugin to a version newer than 4.7.0-3 to receive the security patch, and verify compatibility with the Jenkins instance before deployment.

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
Echarts ApiApplication
Affected:<= 4.7.0-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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 if Jenkins ECharts API Plugin is installed
    Navigate to Manage Jenkins > Manage Plugins > Installed tab, or check the JENKINS_HOME/plugins directory for the echarts-api plugin folder. Look for the plugin named 'ECharts API' or similar.
    Affected if The plugin is not installed or has been removed entirely from the Jenkins instance.
  2. Determine the installed version of the ECharts API Plugin
    In the Installed Plugins page, locate the ECharts API Plugin and note the version number displayed in the Version column. Compare this against the affected range of 4.7.0-3 and earlier.
    Affected if The installed version is 4.7.0-3 or any version lower than 4.7.0-3.
  3. Verify the plugin is enabled and active
    In Manage Jenkins > Manage Plugins > Installed, confirm the ECharts API Plugin shows as 'Enabled' and is not greyed out or marked as disabled.
    Affected if The plugin is currently disabled; however, if it was previously enabled and then disabled after exploitation, the vulnerability may have already been triggered.
  4. Check for build display names in jobs that use trend charts
    Review job configurations for any jobs using the ECharts API Plugin trends or custom charts. Inspect the 'Display Name' field in build histories (found in build URLs under /job/[name]/[buildnumber]/) or in build.xml files in JENKINS_HOME/jobs/[jobname]/builds/[number]/
    Affected if Jobs contain custom build display names and those builds are visible through trend charts rendered by the ECharts API Plugin.
  5. Inspect for existing malicious scripts in build display names
    Search build.xml files in JENKINS_HOME/jobs/*/builds/*/ for any <displayName> elements containing HTML script tags, javascript:, or event handlers like onload, onerror. Alternatively, view build history in the UI and check if display names render as clickable text rather than plain text.
    Affected if Build display names contain unsanitized HTML or JavaScript code that would execute when viewing the trend chart.

The environment is affected if the ECharts API Plugin version is 4.7.0-3 or earlier AND the plugin is enabled while jobs use custom build display names that could contain malicious scripts executed in the trend chart view.

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.

From vendor data
Upgrade available Upgrade to a release after 4.7.0-3
Interim mitigation

Upgrade the Jenkins ECharts API Plugin to a version newer than 4.7.0-3 to receive the security patch, and verify compatibility with the Jenkins instance before deployment.

Fix this in Echarts Api Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $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 $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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