CVE-2020-2314 — jenkinsci-appspider-plugin
LOWCVE-2020-2314 is a low-severity (CVSS 3.3) CWE-522 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.
Password stored in plain text by Jenkins AppSpider Plugin
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2020-2314 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,238 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
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
AppSpider Plugin 1.0.12 and earlier stores a password unencrypted in its global configuration file com.rapid7.jenkinspider.PostBuildScan.xml on the Jenkins controller as part of its configuration.
This password can be viewed by users with access to the Jenkins controller file system.
AppSpider Plugin 1.0.13 stores a password encrypted once its configuration is saved again.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | com.rapid7:jenkinsci-appspider-plugin | all versions | 1.0.13com.rapid7:jenkinsci-appspider-plugin:1.0.13 |
Detection & 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.13 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-2314 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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2020-2314 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2020-2314. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2020-2314 in your dependencies?
O3 Security finds CVE-2020-2314 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.