dbcve.org
Compuware Topaz For Total TestApplication · Jenkins

CVE-2022-43429

HIGH · 7.5 CVSS v3.1 Published 2022-10-19
Fix available
A fix is available. Upgrade to after 2.4.8 or later.
See remediation →
84/100
Remediation priority · High
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 Topaz for Total Test Plugin 2.4.8 and earlier implements an agent/controller message that does not limit where it can be executed, allowing attackers able to control agent processes to read arbitrary files on the Jenkins controller file system.

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 · high confidence

The Jenkins Compuware Topaz for Total Test Plugin versions 2.4.8 and earlier implements an agent/controller message handler that does not properly restrict where arbitrary code can be executed. An attacker who can control agent processes can send specially crafted messages to read any file from the Jenkins controller file system, resulting in arbitrary file read with CVSS 7.5 HIGH severity.

MitigationUpdate the Compuware Topaz for Total Test Plugin to a version later than 2.4.8. Additionally, restrict agent process control to trusted users and monitor for unusual agent-controller communication patterns.

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 Topaz For Total TestApplication
Affected:<= 2.4.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
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 if Compuware Topaz for Total Test Plugin is installed
    Navigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Compuware Topaz for Total Test' in the list of installed plugins.
    Affected if The plugin is not present in the installed plugins list.
  2. Determine the installed version of the plugin
    In the installed plugins list, locate 'Compuware Topaz for Total Test' and note the Version column entry.
    Affected if The version listed is 2.4.8 or earlier.
  3. Check if Jenkins agents are configured
    Navigate to Manage Jenkins > Manage Nodes and review the list of configured agents. Check if any agents exist and whether they are online.
    Affected if Configured agents exist and can be controlled by an attacker, enabling the malformed message attack vector.
  4. Verify plugin is actively loaded
    Check the Jenkins logs at Manage Jenkins > System Log for any errors related to the Compuware Topaz for Total Test plugin during startup, or verify the plugin appears as 'Enabled' in the plugin manager.
    Affected if The plugin is enabled and loaded into Jenkins runtime.

A user is affected if the Compuware Topaz for Total Test plugin version 2.4.8 or earlier is installed, enabled, and Jenkins has configured agents that could be controlled by an attacker to send malformed messages.

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 a release after 2.4.8
Interim mitigation

Update the Compuware Topaz for Total Test Plugin to a version later than 2.4.8. Additionally, restrict agent process control to trusted users and monitor for unusual agent-controller communication patterns.

Recommended fix Moderate confidence

Latest version after 2.4.8 (check Jenkins plugin repository or Compuware official channels for the specific fixed release)

  1. Check the current version of the Compuware Topaz for Total Test Plugin installed in Jenkins via Manage Jenkins > Manage Plugins
  2. Navigate to the Jenkins plugin repository or the Compuware official site to obtain the latest version of the Topaz for Total Test plugin
  3. Upgrade the plugin to the latest available version that addresses CVE-2022-43429
  4. Restart Jenkins or reload configuration as needed to apply the plugin update
  5. Verify the plugin has been updated successfully and test that Topaz for Total Test functionality remains operational
Caveat Review release notes for any breaking changes or configuration requirements when upgrading

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

Fix this in Compuware Topaz For Total Test Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing6.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,840
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-43429 — 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-43429 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