Jenkins Ansible Plugin stores and displays secrets in plain text

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

4.3 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

EPSS

• CVE-2023-32982: 0.38% estimated exploitation activity in the next 30 days; percentile 31.72 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Jenkins Ansible Plugin allows the specification of extra variables that can be passed to Ansible. These extra variables are commonly used to pass secrets. Ansible Plugin 204.v8191fd551ebf and earlier stores these extra variables unencrypted in job config.xml files on the Jenkins controller as part of its configuration. These extra variables can be viewed by users with Item/Extended Read permission or access to the Jenkins controller file system. Additionally, the job configuration form does not mask these extra variables, increasing the potential for attackers to observe and capture them. Ansible Plugin 205.v4cbc48657c21 masks extra variables displayed on the configuration form, and stores them encrypted once job configurations are saved again.

Published by the source

16 May 2023, 18:30 UTC

Last modified by the source

23 Jan 2025, 23:17 UTC

Source last checked

26 Oct 2026, 16:34 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-38hw-368m-7jmg

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2023-32982

Advisory: Jenkins Ansible Plugin stores and displays secrets in plain text
IDs: CVE-2023-32982, GHSA-38hw-368m-7jmg
Record: https://patchnext.com/advisories/cve-2023-32982 (revision 1, source checked 26 Oct 2026, 16:34 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.jenkins-ci.plugins:ansible 205.v4cb. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.jenkins-ci.plugins:ansible: affected < 205.v4cb; fixed in 205.v4cb

## Suggested inspection (read-only)
- Maven org.jenkins-ci.plugins:ansible: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.jenkins-ci.plugins:ansible.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-38hw-368m-7jmg (GitHub-reviewed advisory GHSA-38hw-368m-7jmg lists affected ranges: Maven org.jenkins-ci.plugins:ansible >=0 <205.v4cb)

Commands are suggestions: review each one before running it.