How severe is CVE-2021-21612?

CVE-2021-21612 has a CVSS score of 5.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2021-21612?

CVE-2021-21612 affects the following packages: de.tracetronic.jenkins.plugins:ecutest (Maven). Ecosystems affected: Maven.

How do I fix CVE-2021-21612?

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 CVE-2021-21612 is resolved across your whole dependency graph.

How do I detect CVE-2021-21612 in my Maven dependencies?

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.

How do I mitigate CVE-2021-21612 if there is no patch (or I can't update yet)?

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.

Is CVE-2021-21612 actively exploited in the wild?

No public exploit code has been indexed for CVE-2021-21612 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2021-21612?

CVE-2021-21612 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 27th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2021-21612?

CVE-2021-21612 is classified as CWE-522 (CWE-522). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2021-21612 published, and has it been updated?

CVE-2021-21612 was published on January 13, 2021 and was last updated on October 24, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

MEDIUM severity

CVE-2021-21612 — ecutest

MEDIUM

CVE-2021-21612 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.

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

Also known asGHSA-qvjr-x8fw-hghv

Published

Jan 13, 2021

Updated

Oct 24, 2026

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

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

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`de.tracetronic.jenkins.plugins:ecutest`	all versions	2.24`de.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

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.
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 CVE-2021-21612 is resolved across your whole dependency graph.
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 CVE-2021-21612 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

5.5/10CVSS v3 base

Vector breakdown

Attack Vector

Local

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Raw vector

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

CWE Classification

CWE-522CWE-522

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

Timeline

Disclosed

Jan 13, 2021

Last updated

Oct 24, 2026

Identifiers

CVE-2021-21612

GHSA-qvjr-x8fw-hghv

References

Advisoryjenkins.io · 2021 01 13 Advisorynvd.nist.gov · CVE 2021 21612 Packagegithub.com · ecutest plugin

Related vulnerabilities

Also affects ecutest

This CVE is medium severity; 2 of 2 other CVEs affecting ecutest are rated as high or higher (top: high).

CVE-2018-1999026CVE-2018-1999025

Same weakness: CWE-522

This CVE is medium severity; 6 of 6 other CVEs with CWE-522 are rated as high or higher (top: critical).

CVE-2026-105769CVE-2026-118763CVE-2026-116683GHSA-vqqp-x5qm-5qp4CVE-2026-111765CVE-2026-111763Browse all CWE-522

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 24, 2026

CVE-2021-21612 — ecutest

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2021-21612 in your dependencies?