VncrecorderApplication · Jenkins
CVE-2020-2206
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 · uneditedJenkins VncRecorder Plugin 1.25 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 confidenceThe Jenkins VncRecorder Plugin versions 1.25 and earlier contains a reflected cross-site scripting (XSS) vulnerability in the checkVncServ form validation endpoint. The plugin fails to properly escape a parameter value, allowing an attacker to inject malicious JavaScript that executes in a victim's browser when they submit the vulnerable form.
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
VncrecorderApplication
<= 1.25CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm VncRecorder plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab, or run: jenkins-cli.jar list-plugins (or check /var/lib/jenkins/plugins directory for vnc-recorder*.jpi or similar)Affected if The VncRecorder plugin appears in the installed plugins list
-
Check the installed versionIn Jenkins UI, go to Manage Jenkins > Manage Plugins > Installed and locate VncRecorder to view its version, or inspect the plugin manifest file: /var/lib/jenkins/plugins/vnc-recorder/META-INF/MANIFEST.MFAffected if The version is 1.25 or earlier (versions 1.25 and below are vulnerable)
-
Verify the vulnerable endpoint is accessibleCheck if the checkVncServ form validation endpoint exists by attempting to access: /jenkins/plugin/vncRecorder/checkVncServ (the exact path may vary based on Jenkins configuration)Affected if The endpoint returns a response (indicating it is active)
-
Check for unauthorized access attemptsReview Jenkins access logs and security logs for unusual requests to the vncRecorder endpoint containing suspicious script tags or encoded charactersAffected if Logs contain XSS payloads or anomalous requests to the checkVncServ endpoint
A user is affected if the VncRecorder plugin is installed with version 1.25 or earlier and the checkVncServ endpoint is accessible.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade the VncRecorder Plugin to version 1.26 or later to obtain the fix. If immediate upgrade is not feasible, temporarily disable the plugin or restrict access to the vulnerable endpoint using Jenkins authorization controls.
Fix this in Vncrecorder
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-2206 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-2206 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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