CVE-2020-2219: Stored XSS vulnerability in Jenkins Link Column Plugin

Summary

24/05/2022
No i
Moderate
6.4

CVE-2020-2219: Stored XSS vulnerability in Jenkins Link Column Plugin. Affects org.jenkins-ci.plugins:link-column versions < 1.0. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The Jenkins Link Column Plugin is a Maven-based package that allows users with View/Configure permission to add a new column to list views in Jenkins. This column contains a user-configurable link. The plugin version 1.0 and earlier do not properly filter the URLs for these links, allowing the use of the javascript: scheme. This vulnerability can be exploited by users with the ability to configure list views.

Vulnerability Detail

The vulnerability in the Jenkins Link Column Plugin (CVE-2020-2219) is a stored cross-site scripting (XSS) vulnerability. It arises due to the lack of URL filtering for user-configurable links in list views. Attackers can exploit this vulnerability by injecting malicious JavaScript code into the URL, which will be executed when users access the affected list views. This can lead to various security risks, such as unauthorized access to user data, session hijacking, or the execution of arbitrary code.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a temporary workaround, users can restrict access to the affected list views by limiting the permissions of users who can configure them. Additionally, administrators can manually review and validate the URLs used in the link columns to ensure they do not contain any malicious JavaScript code.

Conclusion

The Jenkins Link Column Plugin is vulnerable to a stored XSS vulnerability that allows attackers to execute arbitrary JavaScript code in the context of affected users. To mitigate this risk, it is crucial to upgrade to a fixed version of the plugin, regularly update Jenkins and its plugins, and follow security best practices. For further assistance and support in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for org.jenkins-ci.plugins:link-column →

Share this vulnerability

FAQ

This vulnerability allows attackers to execute arbitrary JavaScript code in the context of the affected user's browser. Depending on the privileges of the user, this can lead to unauthorized access to sensitive information, session hijacking, or the execution of malicious actions on behalf of the user.

Users with View/Configure permission in Jenkins who are able to add or modify list views with link columns can exploit this vulnerability by injecting malicious JavaScript code into the URL.

There are no known instances of this vulnerability being exploited in the wild. However, it is important to promptly address and fix this vulnerability to prevent potential attacks.

Yes, the CVSS score for this vulnerability is 6.4, indicating a moderate severity level.

You can use Vulert's playground (https://vulert.com/scanner) to check if your application is affected by this vulnerability. Vulert monitors and alerts in real-time for open-source vulnerabilities, using just the pom.xml file to provide insights into the vulnerability status of your software.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback