CVE-2022-43431 — compuware-strobe-measurem…
MEDIUMFix: jenkinsci/compuware-strobe-measurement-plugin@29a0d38CVE-2022-43431 is a medium-severity (CVSS 4.3) CWE-862 vulnerability in com.compuware.jenkins:compuware-strobe-measurement. A fix is available for com.compuware.jenkins:compuware-strobe-measurement — see the affected versions and patch details below.
Jenkins Compuware Strobe Measurement Plugin Missing Authorization vulnerability
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2022-43431.
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-strobe-measurementReal-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 Compuware Strobe Measurement Plugin 1.0.1 and earlier does not perform a permission check in an HTTP endpoint, allowing attackers with Overall/Read permission to enumerate credentials IDs of credentials stored in Jenkins.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | com.compuware.jenkins:compuware-strobe-measurement | all versions | 1.0.2com.compuware.jenkins:compuware-strobe-measurement:1.0.2 |
Affected Products
compuware strobe measurementjenkinsDetection & 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-strobe-measurement, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.compuware.jenkins:compuware-strobe-measurement to 1.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-43431 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-43431 in your dependencies?
Find it across Maven, including transitive dependencies.