dbcve.org
Compuware Xpediter Code CoverageApplication · Jenkins

CVE-2022-43424

MEDIUM · 5.3 CVSS v3.1 Published 2022-10-19
Fix available
A fix is available. Upgrade to 1.0.8 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Jenkins Compuware Xpediter Code Coverage Plugin 1.0.7 and earlier implements an agent/controller message that does not limit where it can be executed, allowing attackers able to control agent processes to obtain the values of Java system properties from the Jenkins controller process.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The Jenkins Compuware Xpediter Code Coverage Plugin versions 1.0.7 and earlier implements an agent-to-controller message mechanism that lacks proper restrictions on execution location. An attacker who has compromised or controls agent processes can send specially crafted messages to the Jenkins controller and retrieve sensitive Java system properties, potentially exposing configuration details, paths, and other environment information.

MitigationUpgrade the Compuware Xpediter Code Coverage Plugin to a version that implements proper restrictions on where agent/controller messages can be executed, limiting them to intended agent processes only.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Compuware Xpediter Code CoverageApplication
Affected:< 1.0.8

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Compuware Xpediter Code Coverage Plugin is installed
    Log into Jenkins and navigate to Manage Jenkins > Manage Plugins > Installed tab, or run this script in Manage Jenkins > Script Console: Jenkins.instance.pluginManager.plugins.findAll { it.shortName == 'compuware-xpediter-code-coverage' }
    Affected if The plugin does not appear in the installed plugins list, meaning the plugin is not present and therefore not affected.
  2. Check the installed plugin version
    In the Installed tab of Manage Plugins, find the Compuware Xpediter Code Coverage entry and note the Version column. Alternatively, run: Jenkins.instance.pluginManager.plugins.find { it.shortName == 'compuware-xpediter-code-coverage' }.version
    Affected if The version is 1.0.7 or earlier (any version below 1.0.8).
  3. Confirm the plugin is active and loaded
    In Manage Jenkins > Script Console, run: Jenkins.instance.getPlugin('compuware-xpediter-code-coverage')?.enabled to check if the plugin is enabled, or verify the plugin status shows 'Enabled' in the Installed plugins list.
    Affected if The plugin is installed and enabled in Jenkins.
  4. Identify if any agents are connected to the controller
    Navigate to Manage Jenkins > Manage Nodes. Review whether any permanent agents or cloud agents are configured and online. You can also run in Script Console: Jenkins.instance.nodes.collect { it.name }
    Affected if There are configured agent nodes, because the vulnerability is exploited through compromised agent processes sending messages to the controller.
  5. Review agent-to-controller message capability
    The plugin implements an agent-to-controller message mechanism. Check if the Compuware Xpediter Code Coverage plugin has any configured endpoints or listeners for agent messages. This can be verified by examining plugin documentation or examining the Jenkins logs for any messages from the compuware-xpediter-code-coverage plugin.
    Affected if The plugin's agent-to-controller message mechanism is active and accessible.

The environment is affected if the Compuware Xpediter Code Coverage Plugin version 1.0.7 or earlier is installed, enabled, and there are agent nodes configured, allowing a compromised agent to send specially crafted messages to retrieve Java system properties.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.0.8 or later
Fixed in 1.0.8
Interim mitigation

Upgrade the Compuware Xpediter Code Coverage Plugin to a version that implements proper restrictions on where agent/controller messages can be executed, limiting them to intended agent processes only.

Recommended fix High confidence

1.0.8

  1. Navigate to the Jenkins dashboard
  2. Go to Manage Jenkins
  3. Go to Manage Plugins
  4. Click on the Installed tab
  5. Locate the Compuware Xpediter Code Coverage plugin
  6. If installed version is earlier than 1.0.8, click 'Update' to upgrade to the latest available version
  7. After update completes, restart Jenkins if required

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Compuware Xpediter Code Coverage Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-43424 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-43424 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data