CVE-2022-36898 — compuware-ispw-operations
MEDIUMCVE-2022-36898 is a medium-severity (CVSS 4.3) CWE-862 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.
Jenkins Compuware ISPW Operations Plugin does not perform permission checks in several HTTP endpoints
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
Jenkins BMC AMI DevX Code Pipeline Operations Plugin 1.0.8 and earlier does not perform permission checks in several HTTP endpoints.
This allows attackers with Overall/Read permission to enumerate hosts and ports of Compuware configurations and credentials IDs of credentials stored in Jenkins. Those credentials IDs can be used as part of an attack to capture the credentials using another vulnerability.
BMC AMI DevX Code Pipeline Operations Plugin 1.0.9 requires the appropriate permissions to enumerate hosts and ports of Compuware configurations and credentials IDs.
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-36898 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
Frequently Asked Questions
Is CVE-2022-36898 in your dependencies?
Find it across Maven, including transitive dependencies.