CVE-2024-28155 — jenkinsci-appspider-plugin
MEDIUMFix: jenkinsci/appspider-build-scanner-plugin@1677f09CVE-2024-28155 is a medium-severity (CVSS 4.3) CWE-862 vulnerability in com.rapid7:jenkinsci-appspider-plugin. A fix is available for com.rapid7:jenkinsci-appspider-plugin — see the affected versions and patch details below.
Jenkins AppSpider Plugin missing permission checks
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-2024-28155.
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.rapid7:jenkinsci-appspider-pluginReal-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 AppSpider Plugin 1.0.16 and earlier does not perform permission checks in several HTTP endpoints, allowing attackers with Overall/Read permission to obtain information about available scan config names, engine group names, and client names.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | com.rapid7:jenkinsci-appspider-plugin | all versions | 1.0.17com.rapid7:jenkinsci-appspider-plugin:1.0.17 |
Affected Products
appspiderjenkinsDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.rapid7:jenkinsci-appspider-plugin, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.rapid7:jenkinsci-appspider-plugin to 1.0.17 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-28155 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-2024-28155 in your dependencies?
Find it across Maven, including transitive dependencies.