dbcve.org
VncviewerApplication · Jenkins

CVE-2020-2207

MEDIUM · 6.1 CVSS v3.1 Published 2020-07-02
Fix available
A fix is available. Upgrade to after 1.7 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 VncViewer Plugin 1.7 and earlier does not escape a parameter value in the checkVncServ form validation endpoint, resulting in a reflected cross-site scripting (XSS) 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 VncViewer Plugin versions 1.7 and earlier fails to escape a parameter value in the checkVncServ form validation endpoint, allowing injection of malicious JavaScript that is reflected back to the user in the response.

MitigationUpdate the Jenkins VncViewer Plugin to a version later than 1.7 which contains the fix for the reflected XSS vulnerability.

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
VncviewerApplication
Affected:<= 1.7

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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. Verify VncViewer plugin is installed
    Access Jenkins Manage Plugins page, go to the Installed tab, and search for VncViewer to confirm the plugin is present in the environment.
    Affected if The plugin is installed and visible in the Jenkins plugin manager
  2. Identify installed VncViewer version
    In Jenkins Manage Plugins > Installed tab, locate the VncViewer plugin entry and note the version number displayed.
    Affected if The installed version is 1.7 or any earlier version (versions 1.0 through 1.7 are all affected)
  3. Confirm checkVncServ endpoint exists
    Attempt to access the form validation endpoint at /plugin/vncviewer/checkVncServ or check if this endpoint responds on the Jenkins instance.
    Affected if The endpoint is accessible and responds to requests, indicating the vulnerable code is in use
  4. Verify plugin is actively used or exposed
    Review Jenkins job configurations or system settings to determine whether any jobs or views expose the VncViewer plugin functionality to users.
    Affected if The plugin functionality is exposed through any job configuration, view, or user-accessible interface

The environment is affected if the VncViewer plugin is installed with version 1.7 or earlier AND the checkVncServ form validation endpoint is accessible to users.

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

Update the Jenkins VncViewer Plugin to a version later than 1.7 which contains the fix for the reflected XSS vulnerability.

Fix this in Vncviewer Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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