CVE-2022-36899 — compuware-ispw-operations
HIGHCVE-2022-36899 is a high-severity (CVSS 8.2) vulnerability in com.compuware.jenkins:compuware-ispw-operations. A fix is available for com.compuware.jenkins:compuware-ispw-operations — see the affected versions and patch details below.
Agent-to-controller security bypass in Jenkins BMC Compuware ISPW Operations plugin
EPSS Exploitation Probability
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
com.compuware.jenkins:compuware-ispw-operationsReal-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
BMC Compuware ISPW Operations Plugin defines a controller/agent message that retrieves Java system properties. BMC Compuware ISPW Operations Plugin 1.0.8 and earlier does not restrict execution of the controller/agent message to agents. This allows attackers able to control agent processes to retrieve Java system properties. This vulnerability is only exploitable in Jenkins 2.318 and earlier, LTS 2.303.2 and earlier. See the LTS upgrade guide. BMC Compuware ISPW Operations plugin 1.0.9 does not allow the affected controller/agent message to be submitted by agents for execution on the controller.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | com.compuware.jenkins:compuware-ispw-operations | all versions | 1.0.9com.compuware.jenkins:compuware-ispw-operations:1.0.9 |
Affected Products
compuware ispw operationsjenkinsDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.compuware.jenkins:compuware-ispw-operations, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.compuware.jenkins:compuware-ispw-operations to 1.0.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-36899 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
Is CVE-2022-36899 in your dependencies?
Find it across Maven, including transitive dependencies.