CVE-2014-3678 — monitoring
Fix: jenkinsci/monitoring-plugin@f0f6aeeCVE-2014-3678 is a Cross-site Scripting (XSS) vulnerability in org.jvnet.hudson.plugins:monitoring. A fix is available for org.jvnet.hudson.plugins:monitoring — see the affected versions and patch details below.
Jenkins Monitoring Plugin allows Cross-Site Scripting (XSS)
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.
Real-World Exposure
org.jvnet.hudson.plugins:monitoringReal-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
Cross-site scripting (XSS) vulnerability in the Monitoring plugin before 1.53.0 for Jenkins allows remote attackers to inject arbitrary web script or HTML via unspecified vectors.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.jvnet.hudson.plugins:monitoring | all versions | 1.53.0org.jvnet.hudson.plugins:monitoring:1.53.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jvnet.hudson.plugins:monitoring, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jvnet.hudson.plugins:monitoring to 1.53.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-3678 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-2014-3678 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2014-3678. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat OpenShift Enterprise 2.1 | jenkins-0:1.565.3-1.el6op | RHBA-2014:1630 |
Frequently Asked Questions
Is CVE-2014-3678 in your dependencies?
O3 Security finds CVE-2014-3678 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.