Compuware Zadviser ApiApplication · Jenkins
CVE-2022-36900
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 zAdviser API Plugin 1.0.3 and earlier does not restrict execution of a controller/agent message to agents, allowing attackers able to control agent processes to retrieve Java system properties.
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 confidenceThe Jenkins Compuware zAdviser API Plugin fails to restrict controller/agent message execution to the controller side only. Attackers who compromise agent processes can send messages to the controller that cause it to return Java system properties, exposing sensitive configuration data.
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 Zadviser ApiApplication
<= 1.0.3CVSS 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
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/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.
-
Check if Compuware zAdviser API plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'zAdviser' or 'Compuware', or run: jenkins-cli.jar who-am-i (if available) or inspect $JENKINS_HOME/plugins for zadviser folderAffected if The plugin folder $JENKINS_HOME/plugins/zadviser exists or the plugin appears in the installed plugins list
-
Determine installed plugin versionIn Jenkins UI, go to Manage Jenkins > Manage Plugins > Installed tab, find Compuware zAdviser API, and note the Version column. Alternatively, inspect $JENKINS_HOME/plugins/zadviser/META-INF/MANIFEST.MF for the Plugin-Version attributeAffected if The version is 1.0.3 or lower
-
Check if Jenkins agents are configuredNavigate to Manage Jenkins > Manage Nodes and Clouds. Review the list of configured agents (nodes). Alternatively, check for agent-related XML/JSON files in $JENKINS_HOME/nodesAffected if Any permanent agents or cloud agents are configured and online, as compromised agents are the attack vector
-
Review controller logs for unexpected agent-to-controller messagesExamine Jenkins logs (Manage Jenkins > System Log > All Jenkins Logs) or $JENKINS_HOME/logs for entries containing 'zAdviser' or 'system properties' requests originating from agent connections, especially at unexpected times or from untrusted agentsAffected if Logs show zAdviser-related messages or system property requests from agent nodes that were not initiated by legitimate controller-side automation
A user is affected if the Compuware zAdviser API plugin version 1.0.3 or lower is installed AND Jenkins agents are configured, allowing a compromised agent to request system properties from the controller.
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.
From vendor dataUpdate to plugin version 1.0.4 or later when available. Until then, limit access to who can control Jenkins agent processes and monitor for unauthorized agent-to-controller messages.
Fix this in Compuware Zadviser Api
Scoped from the published advisory
- Consultation2.0 h
- Implementation8.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 $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-36900 — 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-36900 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