Vulnerabilities > Jenkins > Electricflow > 1.0
| DATE | CVE | VULNERABILITY TITLE | RISK |
|---|---|---|---|
| 2019-06-11 | CVE-2019-10336 | Cross-site Scripting vulnerability in Jenkins Electricflow A reflected cross site scripting vulnerability in Jenkins ElectricFlow Plugin 1.1.6 and earlier allowed attackers able to control the output of the ElectricFlow API to inject arbitrary HTML and JavaScript in job configuration forms containing post-build steps provided by this plugin. | 6.1 |
| 2019-06-11 | CVE-2019-10335 | Cross-site Scripting vulnerability in Jenkins Electricflow A stored cross site scripting vulnerability in Jenkins ElectricFlow Plugin 1.1.5 and earlier allowed attackers able to configure jobs in Jenkins or control the output of the ElectricFlow API to inject arbitrary HTML and JavaScript in the plugin-provided output on build status pages. | 5.4 |
| 2019-06-11 | CVE-2019-10334 | Improper Certificate Validation vulnerability in Jenkins Electricflow Jenkins ElectricFlow Plugin 1.1.5 and earlier disabled SSL/TLS and hostname verification globally for the Jenkins master JVM when MultipartUtility.java is used to upload files. | 6.5 |
| 2019-06-11 | CVE-2019-10333 | Missing Authorization vulnerability in Jenkins Electricflow Missing permission checks in Jenkins ElectricFlow Plugin 1.1.5 and earlier in various HTTP endpoints allowed users with Overall/Read access to obtain information about the Jenkins ElectricFlow Plugin configuration and configuration of connected ElectricFlow instances. | 4.3 |
| 2019-06-11 | CVE-2019-10332 | Missing Authorization vulnerability in Jenkins Electricflow A missing permission check in Jenkins ElectricFlow Plugin 1.1.5 and earlier in Configuration#doTestConnection allowed users with Overall/Read access to connect to an attacker-specified URL using attacker-specified credentials. | 4.3 |
| 2019-06-11 | CVE-2019-10331 | Cross-Site Request Forgery (CSRF) vulnerability in Jenkins Electricflow A cross-site request forgery vulnerability in Jenkins ElectricFlow Plugin 1.1.5 and earlier in Configuration#doTestConnection allowed attackers to connect to an attacker-specified URL using attacker-specified credentials. | 4.3 |