CVE-2021-21700: Stored XSS vulnerability in Jenkins Scriptler Plugin

Summary

24/05/2022
Yes i
Moderate
5.4

CVE-2021-21700: Stored XSS vulnerability in Jenkins Scriptler Plugin. Affects org.jenkins-ci.plugins:scriptler versions < 3.4. Fixed in 3.4. 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 Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The Jenkins Scriptler Plugin is a tool that allows users to define and manage scripts within the Jenkins automation server. It provides a user interface for creating, editing, and executing scripts that can be used for various tasks in the Jenkins environment. The plugin is widely used by developers and administrators to automate workflows and customize Jenkins functionality.

Vulnerability Detail

The Scriptler Plugin version 3.3 and earlier are affected by a stored cross-site scripting (XSS) vulnerability. This vulnerability arises from the plugin's failure to properly escape the name of scripts on the user interface when confirming their deletion. As a result, an attacker with the ability to create Scriptler scripts can exploit this vulnerability to inject malicious code into the Jenkins environment. This can lead to unauthorized access, data theft, and potential compromise of the entire Jenkins server.

How To Fix

Minimum fixed version

3.4

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

If immediate upgrade to version 3.4 is not possible, users can mitigate the risk by implementing the following workaround:

  1. Disable the ability for users to create or modify Scriptler scripts.
  2. Regularly review and delete any existing Scriptler scripts that are not necessary.

By limiting the creation and modification of scripts and removing unnecessary scripts, the attack surface for this vulnerability can be reduced.

Conclusion

The Jenkins Scriptler Plugin version 3.3 and earlier are affected by a stored XSS vulnerability that can be exploited by attackers with the ability to create Scriptler scripts. Upgrading to version 3.4 or later is recommended to mitigate this vulnerability. In the meantime, users can implement the provided workaround to reduce the risk. For further support and assistance in vulnerability remediation, please contact DevNack.com.

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

Share this vulnerability

FAQ

The vulnerability allows an attacker to execute arbitrary code within the Jenkins environment, potentially leading to unauthorized access, data theft, and compromise of the entire Jenkins server.

Users of Jenkins Scriptler Plugin versions 3.3 and earlier are affected by this vulnerability. It is recommended for all users of the plugin to upgrade to version 3.4 or later.

There are no known public exploits for this vulnerability at the time of this report. However, it is important to promptly apply the recommended fix to mitigate the risk.

No, this vulnerability requires an attacker to have the ability to create Scriptler scripts within the Jenkins environment. It cannot be exploited remotely without prior access.

There is no evidence of active exploitation of this vulnerability at the time of this report. However, it is crucial to apply the recommended fix to prevent potential future attacks.

Related vulnerabilities

Recent vulnerabilities recorded for org.jenkins-ci.plugins:scriptler.

How To Fix

Minimum fixed version

3.4

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. 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