NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
MEDIUM severity

Credentials stored in plain text by Jenkins TraceTronic ECU-TEST PluginGHSA-qvjr-x8fw-hghv

MEDIUM

GHSA-qvjr-x8fw-hghv is a medium-severity (CVSS 5.5) CWE-522 vulnerability in de.tracetronic.jenkins.plugins:ecutest. A fix is available for de.tracetronic.jenkins.plugins:ecutest — see the affected versions and patch details below.

Also known asCVE-2021-21612
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 2, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
0.3%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs27th percentile — riskier than 27% of all scored CVEsHighest risk
0.00%0.28%0.56%0.84%0.0%0.3%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected
☕de.tracetronic.jenkins.plugins:ecutest

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
☕Mavende.tracetronic.jenkins.plugins:ecutestall versions2.24de.tracetronic.jenkins.plugins:ecutest:2.24

Affected Products

1 product · 1 configurations
Application
tracetronic ecu-testjenkins
≤ 2.23.1
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for de.tracetronic.jenkins.plugins:ecutest, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update de.tracetronic.jenkins.plugins:ecutest to 2.24 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qvjr-x8fw-hghv is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is GHSA-qvjr-x8fw-hghv in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
Credentials stored in plain text by Jenkins TraceTronic…