Compuware Topaz For Total TestApplication · Jenkins
CVE-2022-43428
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 · uneditedJenkins 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 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 confidenceThe Jenkins Compuware Topaz for Total Test Plugin versions 2.4.8 and earlier has an agent/controller message implementation that does not restrict execution location. An attacker with control over agent processes can send specially crafted messages to obtain Java system properties from the Jenkins controller process, leading to information disclosure.
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
<= 2.4.8CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify Compuware Topaz for Total Test Plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed and search for 'Compuware Topaz for Total Test' in the list of installed pluginsAffected if The plugin appears in the installed plugins list
-
Determine the installed plugin versionIn the installed plugins list, locate the Compuware Topaz for Total Test plugin and note the Version column valueAffected if The version is 2.4.8 or earlier (versions 2.4.8 and all prior versions are affected)
-
Confirm agent connectivityNavigate to Manage Jenkins > Manage Nodes and review the list of connected agents. Check if any agents are configured and connected to the Jenkins controllerAffected if Any agent nodes are connected - the vulnerability requires an attacker to have control over agent processes to send malicious messages
-
Check agent process permissionsReview agent configuration in Manage Nodes. Examine whether agent processes run with elevated privileges or have access to sensitive system resourcesAffected if Agents run with permissions that could allow access to Java system properties or sensitive controller data
You are affected if the Compuware Topaz for Total Test plugin is installed at version 2.4.8 or earlier and any agent nodes are connected to the controller, since the vulnerability allows a compromised agent to retrieve Java system properties from the controller process.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpdate the Compuware Topaz for Total Test Plugin to a version later than 2.4.8. Additionally, restrict agent process permissions and implement proper validation on agent/controller message handlers to ensure messages can only execute in intended contexts.
Compuware Topaz for Total Test version 2.4.9 or later
- Navigate to the Jenkins dashboard
- Go to Manage Jenkins > Manage Plugins
- Click on the 'Installed' tab
- Locate 'Compuware Topaz for Total Test' in the list
- If an update is available, select it and click 'Download now and install after restart'
- Wait for the plugin to update and Jenkins to restart
- Verify the updated version is installed (should be version 2.4.9 or later)
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
- Consultation3.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-43428 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-43428 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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