How severe is CVE-2022-43424?

CVE-2022-43424 has a CVSS score of 4.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2022-43424?

CVE-2022-43424 affects the following packages: com.compuware.jenkins:compuware-xpediter-code-coverage (Maven). Ecosystems affected: Maven.

How do I fix CVE-2022-43424?

Update com.compuware.jenkins:compuware-xpediter-code-coverage to 1.0.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-43424 is resolved across your whole dependency graph.

How do I detect CVE-2022-43424 in my Maven dependencies?

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

How do I mitigate CVE-2022-43424 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-2022-43424 actively exploited in the wild?

No public exploit code has been indexed for CVE-2022-43424 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-2022-43424?

CVE-2022-43424 has an EPSS (Exploit Prediction Scoring System) score of 0.8%, placing it in the 57th 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-2022-43424?

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

When was CVE-2022-43424 published, and has it been updated?

CVE-2022-43424 was published on October 19, 2022 and was last updated on February 16, 2024. 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-2022-43424 — compuware-xpediter-code-c…

MEDIUMFix: jenkinsci/compuware-xpediter-code-coverage-plugin@e506fc9

CVE-2022-43424 is a medium-severity (CVSS 4.3) CWE-693 vulnerability in com.compuware.jenkins:compuware-xpediter-code-coverage. A fix is available for com.compuware.jenkins:compuware-xpediter-code-coverage — see the affected versions and patch details below.

Agent-to-controller security bypass vulnerability in Jenkins Compuware Xpediter Code Coverage Plugin

Published

Oct 19, 2022

Updated

Feb 16, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2022-43424.

EPSS Exploitation Probability

via FIRST.org ↗

0.8%probability of exploitation in next 30 days

Lower Risk+0.01%

Lower risk than most CVEs57th percentile — riskier than 57% 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

☕com.compuware.jenkins:compuware-xpediter-code-coverage

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

Compuware Xpediter Code Coverage Plugin 1.0.7 and earlier implements an agent/controller message that does not limit where it can be executed.

It allows attackers able to control agent processes to obtain the values of Java system properties from the Jenkins controller process.

This vulnerability is only exploitable in Jenkins 2.318 and earlier, LTS 2.303.2 and earlier. See the LTS upgrade guide.

Compuware Xpediter Code Coverage Plugin 1.0.8 restricts execution of the agent/controller message to agents.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.compuware.jenkins:compuware-xpediter-code-coverage`	all versions	1.0.8`com.compuware.jenkins:compuware-xpediter-code-coverage:1.0.8`

Affected Products

1 product · 1 configurations

Application

compuware xpediter code coveragejenkins

< 1.0.8

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.compuware.jenkins:compuware-xpediter-code-coverage, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.compuware.jenkins:compuware-xpediter-code-coverage to 1.0.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-43424 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

Compuware Xpediter Code Coverage Plugin 1.0.7 and earlier implements an agent/controller message that does not limit where it can be executed. It allows attackers able to control agent processes to obtain the values of Java system properties from the Jenkins controller process. This vulnerability is only exploitable in Jenkins 2.318 and earlier, LTS 2.303.2 and earlier. See the [LTS upgrade guide](https://www.jenkins.io/doc/upgrade-guide/2.303/#upgrading-to-jenkins-lts-2-303-3). Compuware Xpediter Code Coverage Plugin 1.0.8 restricts execution of the agent/controller message to agents.

O3 Security · Impact-Aware SCA

Is CVE-2022-43424 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

4.3/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

None

Availability

None

Raw vector

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

CWE Classification

CWE-693CWE-693

Weaponization

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

Timeline

Disclosed

Oct 19, 2022

Last updated

Feb 16, 2024

Identifiers

CVE-2022-43424

References

Advisorynvd.nist.gov · CVE 2022 43424 Webgithub.com · e506fc9e77a2609f6a5aa331e052d35be652071c Webjenkins.io · 2022 10 19 Webopenwall.com Packagegithub.com · compuware xpediter code coverage plugin

Related vulnerabilities

Also affects compuware-xpediter-code-coverage

This CVE is medium severity, in line with the other 1 CVE affecting compuware-xpediter-code-coverage.

CVE-2022-36897

Same weakness: CWE-693

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

CVE-2026-44267CVE-2026-61438CVE-2026-114614CVE-2026-114139GHSA-mrv2-3pqr-j5jrCVE-2026-113730CVE-2026-94603Browse all CWE-693

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedFeb 16, 2024

CVE-2022-43424 — compuware-xpediter-code-c…

Exploitation Status

No confirmed exploitation observed yet

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-2022-43424 in your dependencies?