CVE-2020-2209: Password stored in plain text by Jenkins TestComplete support Plugin

Summary

24/05/2022
Yes i
Moderate
4.3

CVE-2020-2209: Password stored in plain text by Jenkins TestComplete support Plugin. Affects org.jenkins-ci.plugins:TestComplete versions < 2.5.2. Fixed in 2.5.2. 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

Jenkins TestComplete support Plugin is a Maven package that provides integration between Jenkins and TestComplete, a functional testing platform. It allows users to execute TestComplete tests as part of their Jenkins build process. The plugin stores configuration information in job config.xml files on the Jenkins master. However, prior to version 2.5.2, it stored passwords in plain text, making them vulnerable to unauthorized access.

Vulnerability Detail

The vulnerability (CVE-2020-2209) in Jenkins TestComplete support Plugin allows passwords to be stored in plain text in job config.xml files on the Jenkins master. This means that users with Extended Read permission or access to the master file system can view these passwords. The issue poses a moderate risk as it could lead to unauthorized access to sensitive information. The vulnerability has a CVSS score of 4.3.

How To Fix

Minimum fixed version

2.5.2

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

There is no specific workaround mentioned for this vulnerability. However, users can mitigate the risk by ensuring that only trusted individuals have access to the Jenkins master file system and by restricting Extended Read permission to authorized personnel.

Conclusion

In conclusion, the Jenkins TestComplete support Plugin prior to version 2.5.2 stores passwords in plain text, making them vulnerable to unauthorized access. To mitigate this risk, it is recommended to upgrade to version 2.5.2 or later, which includes a patch that encrypts the stored passwords. For further support on vulnerability remediation, please contact DevNack.com.

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

Share this vulnerability

FAQ

Jenkins TestComplete support Plugin is a Maven package that integrates Jenkins and TestComplete, allowing users to execute TestComplete tests as part of their Jenkins build process.

The vulnerability allows passwords to be stored in plain text, making them accessible to users with Extended Read permission or access to the Jenkins master file system. This could lead to unauthorized access to sensitive information.

The CVSS score of this vulnerability is 4.3, indicating a moderate risk.

To fix this vulnerability, upgrade to version 2.5.2 or later of the Jenkins TestComplete support Plugin, which includes a patch that encrypts the stored passwords.

While there is no specific workaround mentioned, users can mitigate the risk by restricting access to the Jenkins master file system and limiting Extended Read permission to authorized personnel.

Related vulnerabilities

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

How To Fix

Minimum fixed version

2.5.2

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