CVE-2020-2324: XXE vulnerability in Jenkins CVS Plugin

org.jenkins-ci.plugins:cvs Updated 02 Oct 2025

Summary

24/05/2022
Yes i
High
7.5

CVE-2020-2324: XXE vulnerability in Jenkins CVS Plugin. Affects org.jenkins-ci.plugins:cvs versions < 2.17. Fixed in 2.17. 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 CVS Plugin is a Maven package that provides integration between Jenkins and CVS repositories. It allows users to manage and automate build processes using CVS as the version control system. The plugin enables Jenkins to interact with CVS repositories, perform checkouts, and retrieve changelogs.

The vulnerability identified as CVE-2020-2324 is an XML External Entity (XXE) vulnerability present in CVS Plugin versions 2.16 and earlier. These versions do not configure their XML parser to prevent XXE attacks. As a result, an attacker who can control an agent process can exploit this vulnerability to make Jenkins parse a specially crafted changelog file. This file can contain external entities that extract sensitive information from the Jenkins controller or enable server-side request forgery.

To address this issue, CVS Plugin version 2.17 has been released, which disables external entity resolution for its XML parser.

Vulnerability Detail

The XXE vulnerability in Jenkins CVS Plugin (CVE-2020-2324) arises from the lack of proper configuration of the XML parser in versions 2.16 and earlier. This vulnerability allows an attacker with control over an agent process to manipulate a changelog file and exploit external entities to extract sensitive information or perform server-side request forgery. The impact of this vulnerability can be severe, as it can lead to unauthorized access to sensitive data or enable further attacks on the Jenkins infrastructure.

How To Fix

Minimum fixed version

2.17

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

As a temporary workaround, users can disable the Jenkins CVS Plugin if it is not essential for their build processes. Disabling the plugin will remove the vulnerability from the system. To disable the plugin, navigate to the 'Manage Plugins' section in Jenkins, select the 'Installed' tab, locate the CVS Plugin, and uncheck the checkbox next to it. After disabling the plugin, it is recommended to monitor for any updates or patches that address the vulnerability and re-enable the plugin once a fix is available.

Conclusion

The XXE vulnerability in Jenkins CVS Plugin (CVE-2020-2324) poses a significant risk to Jenkins installations using versions 2.16 and earlier. It allows attackers to extract sensitive information or perform server-side request forgery. To mitigate this vulnerability, it is crucial to update the plugin to version 2.17 or later, which disables external entity resolution. Alternatively, users can temporarily disable the plugin if it is not essential for their build processes. For further support and assistance in vulnerability remediation, please contact DevNack.com.

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

Share this vulnerability

FAQ

The XXE vulnerability in Jenkins CVS Plugin can allow an attacker to extract sensitive information from the Jenkins controller or perform server-side request forgery. This can lead to unauthorized access to confidential data or enable further attacks on the Jenkins infrastructure.

You can use the Vulert Playground (https://vulert.com/scanner) to check if your Jenkins installation is affected by this vulnerability. Vulert monitors and alerts in real-time for open-source vulnerabilities, including the Jenkins CVS Plugin XXE vulnerability, using only the pom.xml file.

Yes, a temporary workaround is to disable the Jenkins CVS Plugin if it is not essential for your build processes. This will remove the vulnerability from the system. However, it is recommended to monitor for updates or patches and re-enable the plugin once a fix is available.

The CVSS score of the Jenkins CVS Plugin XXE vulnerability is 7.1, indicating a high severity level.

For more information about the Jenkins CVS Plugin XXE vulnerability (CVE-2020-2324), you can refer to the GitHub Security Advisory database (https://github.com/github/advisory-database) or contact the Jenkins community for assistance.

Related vulnerabilities

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

How To Fix

Minimum fixed version

2.17

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