CVE-2022-34184: Cross-site Scripting in Jenkins CRX Content Package Deployer Plugin

Summary

24/06/2022
No i
High
8.0

CVE-2022-34184: Cross-site Scripting in Jenkins CRX Content Package Deployer Plugin. Affects org.jenkins-ci.plugins:crx-content-package-deployer versions < 1.9. 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 CRX Content Package Deployer Plugin is a Maven-based plugin that allows users to deploy CRX content packages in Jenkins. It provides functionality for managing and deploying content packages to Adobe Experience Manager (AEM) instances. The plugin is widely used in Jenkins environments for automating the deployment process of AEM applications.

Vulnerability Detail

The Jenkins CRX Content Package Deployer Plugin version 1.9 and earlier is vulnerable to a stored cross-site scripting (XSS) attack. The plugin fails to properly escape the name and description of CRX Content Package Choice parameters when displaying them on certain views. This vulnerability can be exploited by attackers with Item/Configure permission. To exploit this vulnerability, the parameters need to be listed on pages like 'Build With Parameters' and 'Parameters' pages provided by Jenkins. If these pages are not hardened to prevent exploitation, an attacker can inject malicious scripts into the parameter values, leading to potential XSS attacks. Jenkins (core) has addressed similar vulnerabilities in the past, but this specific plugin version remains vulnerable.

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 manually sanitize the parameter values by escaping special characters and removing any potentially malicious scripts. However, this workaround is not recommended as it requires manual intervention and may not provide complete protection against XSS attacks. It is strongly advised to apply the official fix by upgrading the plugin to the latest version.

Conclusion

The Jenkins CRX Content Package Deployer Plugin version 1.9 and earlier is vulnerable to a stored XSS attack. To mitigate the risk, users should upgrade to version 1.10 or later. It is crucial to keep software up to date and follow security best practices to minimize the risk of exploitation. For further assistance and support in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for org.jenkins-ci.plugins:crx-content-package-deployer →

Share this vulnerability

FAQ

This vulnerability allows attackers with Item/Configure permission to inject malicious scripts into the parameter values of the Jenkins CRX Content Package Deployer Plugin. If successfully exploited, an attacker can execute arbitrary code in the context of the affected user, potentially compromising the Jenkins environment and its associated resources.

No, only versions 1.9 and earlier of the Jenkins CRX Content Package Deployer Plugin are affected by this vulnerability. It is recommended to upgrade to version 1.10 or later to mitigate the risk.

While there is no known public exploit for this vulnerability at the time of this report, it is important to address it promptly to prevent potential exploitation. Attackers are constantly looking for vulnerabilities in popular plugins like Jenkins, and it is crucial to keep software up to date to minimize the risk of exploitation.

No, this vulnerability requires attackers to have Item/Configure permission in the Jenkins environment. It cannot be exploited remotely without authenticated access to the Jenkins instance.

At the time of this report, there are no known alternative plugins specifically designed to replace the functionality of the Jenkins CRX Content Package Deployer Plugin. However, it is always recommended to regularly review and update plugins to ensure the latest security patches are applied.

Related vulnerabilities

Recent vulnerabilities recorded for org.jenkins-ci.plugins:crx-content-package-deployer.

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