CVE-2023-32982: Jenkins Ansible Plugin stores and displays secrets in plain text

Summary

16/05/2023
Yes i
Moderate
4.3

CVE-2023-32982: Jenkins Ansible Plugin stores and displays secrets in plain text. Affects org.jenkins-ci.plugins:ansible versions < 205.v4cb. Fixed in 205.v4cb. 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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The Jenkins Ansible Plugin is a tool that allows users to specify extra variables to be passed to Ansible, commonly used for passing secrets. The plugin version 204.v8191fd551eb_f and earlier stores these extra variables unencrypted in job config.xml files on the Jenkins controller. This means that anyone with Item/Extended Read permission or access to the Jenkins controller file system can view these secrets. Additionally, the job configuration form does not mask these extra variables, making it easier for attackers to observe and capture them. The plugin version 205.v4cb_c48657c21 addresses this issue by masking the extra variables on the configuration form and storing them encrypted once job configurations are saved again.

Vulnerability Detail

The vulnerability in the Jenkins Ansible Plugin allows secrets to be stored and displayed in plain text. This means that unauthorized users with access to the Jenkins controller or job config.xml files can view these secrets. The lack of encryption and masking increases the risk of attackers capturing sensitive information. The vulnerability has a CVSS score of 4.3, indicating a moderate severity level.

How To Fix

Minimum fixed version

205.v4cb

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. The recommended solution is to upgrade to the latest version of the Jenkins Ansible Plugin.

Conclusion

The Jenkins Ansible Plugin vulnerability allows secrets to be stored and displayed in plain text, increasing the risk of unauthorized access and misuse. Users are advised to upgrade to the latest version of the plugin to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.

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

Share this vulnerability

FAQ

This vulnerability allows unauthorized users to view and capture secrets stored in the Jenkins Ansible Plugin. This can lead to the exposure of sensitive information and potential misuse by attackers.

Users of Jenkins Ansible Plugin versions 204.v8191fd551eb_f and earlier are affected by this vulnerability.

There are no known exploits for this vulnerability at the moment. However, the lack of encryption and masking of secrets increases the risk of potential attacks.

Yes, the fix for this vulnerability is available in version 205.v4cb_c48657c21 or later of the Jenkins Ansible Plugin.

You can use the Vulert Playground (https://vulert.com/scanner) to check if your Jenkins Ansible Plugin version is affected by this vulnerability. Simply enter your pom.xml file and the playground will provide real-time alerts for open-source vulnerabilities.

Related vulnerabilities

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

How To Fix

Minimum fixed version

205.v4cb

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