Credentials stored in plain text by Jenkins TraceTronic ECU-TEST Plugin

Exploitation

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

CVSS

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

EPSS

• CVE-2021-21612: 0.34% estimated exploitation activity in the next 30 days; percentile 27.27 (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 TraceTronic ECU-TEST Plugin 2.23.1 and earlier stores credentials unencrypted in its global configuration file de.tracetronic.jenkins.plugins.ecutest.report.atx.installation.ATXInstallation.xml on the Jenkins controller as part of its configuration. These credentials can be viewed by users with access to the Jenkins controller file system. Jenkins TraceTronic ECU-TEST Plugin 2.24 adds a new option type for sensitive options. Previously stored credentials are migrated to that option type on Jenkins startup.

Published by the source

24 May 2022, 17:39 UTC

Last modified by the source

27 Oct 2023, 13:26 UTC

Source last checked

26 Oct 2026, 16:15 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-qvjr-x8fw-hghv

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

# Patch Next advisory brief: CVE-2021-21612

Advisory: Credentials stored in plain text by Jenkins TraceTronic ECU-TEST Plugin
IDs: CVE-2021-21612, GHSA-qvjr-x8fw-hghv
Record: https://patchnext.com/advisories/cve-2021-21612 (revision 1, source checked 26 Oct 2026, 16:15 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: de.tracetronic.jenkins.plugins:ecutest 2.24. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven de.tracetronic.jenkins.plugins:ecutest: affected <= 2.23.1; fixed in 2.24

## Suggested inspection (read-only)
- Maven de.tracetronic.jenkins.plugins:ecutest: 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 de.tracetronic.jenkins.plugins:ecutest.
- 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-qvjr-x8fw-hghv (GitHub-reviewed advisory GHSA-qvjr-x8fw-hghv lists affected ranges: Maven de.tracetronic.jenkins.plugins:ecutest >=0 <=2.23.1)

Commands are suggestions: review each one before running it.