October 16, 2019
Jenkins plugins are prone to the following vulnerabilities: 1. Multiple cross-site request forgery vulnerabilities 2. Multiple information disclosure vulnerabilities 3. Multiple security-bypass vulnarabilites An attacker may leverage these issues to execute arbitrary script code in the browser of the victim in the context of the affected site, steal cookie-based authentication credentials, gain access to sensitive information, perform certain administrative actions and gain unauthorized access to the affected application. This may aid in further attacks. The following Jenkins plugins versions are vulnerable: Bumblebee HP ALM Plugin through 4.1.3 Cadence vManager Plugin through 2.7.0 CRX Content Package Deployer Plugin through 1.8.1 Delphix Plugin through 2.0.4 ElasticBox CI Plugin through 5.0.1 Extensive Testing Plugin through 1.4.4b Fortify on Demand Plugin through 4.0.0 Google Kubernetes Engine Plugin through 0.7.0 Google OAuth Credentials Plugin through 0.9 iceScrum Plugin through 1.1.5 NeoLoad Plugin through 2.2.5 Oracle Cloud Infrastructure Compute Classic Plugin through 1.0.0 Puppet Enterprise Pipeline Plugin through 1.3.1 Rundeck Plugin through 3.6.5 SOASTA CloudTest Plugin through 2.25 Sofy.AI Plugin through 1.0.3 View26 Test-Reporting Plugin through 1.0.7
- Jenkins Bumblebee HP ALM 3.0.0
- Jenkins Bumblebee HP ALM 4.0.0
- Jenkins Bumblebee HP ALM 4.1.0
- Jenkins Bumblebee HP ALM 4.1.1
- Jenkins Bumblebee HP ALM 4.1.2
- Jenkins Bumblebee HP ALM 4.1.3
- Jenkins CRX Content Package Deployer 1.4
- Jenkins CRX Content Package Deployer 1.6
- Jenkins CRX Content Package Deployer 1.7
- Jenkins CRX Content Package Deployer 1.8
- Jenkins Cadence vManager 2.5.0
- Jenkins Cadence vManager 2.6.0
- Jenkins Cadence vManager 2.7.0
- Jenkins Delphix 2.0.0
- Jenkins Delphix 2.0.1
- Jenkins Delphix 2.0.2
- Jenkins Delphix 2.0.3
- Jenkins Delphix 2.0.4
- Jenkins ElasticBox CI 4.0.0
- Jenkins ElasticBox CI 5.0.0
- Jenkins ElasticBox CI 5.0.1
- Jenkins Extensive Testing 1.4.4b
- Jenkins Fortify on Demand 3.0.4
- Jenkins Fortify on Demand 3.0.5
- Jenkins Fortify on Demand 3.0.6
- Jenkins Fortify on Demand 3.0.8
- Jenkins Fortify on Demand 4.0.0
- Jenkins Google Kubernetes Engine 0.1.0
- Jenkins Google Kubernetes Engine 0.3.0
- Jenkins Google Kubernetes Engine 0.4.0
- Jenkins Google Kubernetes Engine 0.5.0
- Jenkins Google Kubernetes Engine 0.6.0
- Jenkins Google Kubernetes Engine 0.6.1
- Jenkins Google Kubernetes Engine 0.6.2
- Jenkins Google Kubernetes Engine 0.6.3
- Jenkins Google Kubernetes Engine 0.7.0
- Jenkins Google OAuth Credentials 0.1
- Jenkins Google OAuth Credentials 0.2
- Jenkins Google OAuth Credentials 0.3
- Jenkins Google OAuth Credentials 0.4
- Jenkins Google OAuth Credentials 0.5
- Jenkins Google OAuth Credentials 0.6
- Jenkins Google OAuth Credentials 0.7
- Jenkins Google OAuth Credentials 0.8
- Jenkins Google OAuth Credentials 0.9
- Jenkins NeoLoad 2.2.1
- Jenkins NeoLoad 2.2.2
- Jenkins NeoLoad 2.2.3
- Jenkins NeoLoad 2.2.4
- Jenkins NeoLoad 2.2.5
- Jenkins Oracle Cloud Infrastructure Compute Classic 1.0.0
- Jenkins Rundeck 3.6.1
- Jenkins Rundeck 3.6.2
- Jenkins Rundeck 3.6.3
- Jenkins Rundeck 3.6.4
- Jenkins Rundeck 3.6.5
- Jenkins SOASTA CloudTest 2.20
- Jenkins SOASTA CloudTest 2.21
- Jenkins SOASTA CloudTest 2.22
- Jenkins SOASTA CloudTest 2.23
- Jenkins SOASTA CloudTest 2.24
- Jenkins SOASTA CloudTest 2.25
- Jenkins SOASTA CloudTest 2.26
- Jenkins SOASTA CloudTest 2.27
- Jenkins Sofy.AI 1.0
- Jenkins Sofy.AI 1.0.1
- Jenkins Sofy.AI 1.0.3
- Jenkins View26 Test-Reporting 1.0.1
- Jenkins View26 Test-Reporting 1.0.2
- Jenkins View26 Test-Reporting 1.0.3
- Jenkins View26 Test-Reporting 1.0.4
- Jenkins View26 Test-Reporting 1.0.5
- Jenkins View26 Test-Reporting 1.0.6
- Jenkins View26 Test-Reporting 1.0.7
- Jenkins iceScrum 1.1.1
- Jenkins iceScrum 1.1.2
- Jenkins iceScrum 1.1.3
- Jenkins iceScrum 1.1.4
- Jenkins iceScrum 1.1.5
Block external access at the network boundary, unless external parties require service.
Filter access to the affected computer at the network boundary if global access isn't needed. Restricting access to only trusted computers and networks might greatly reduce the likelihood of a successful exploit.
Deploy network intrusion detection systems to monitor network traffic for malicious activity.
Deploy NIDS to detect and block attacks and anomalous activity such as requests containing suspicious URI sequences. Since the webserver may log such requests, review its logs regularly.
Do not follow links provided by unknown or untrusted sources.
Web users should be cautious about following links to sites that are provided by unfamiliar or suspicious sources. Filtering HTML from emails may help remove a possible vector for transmitting malicious links to users.
When possible, limit the privileges granted to users to the least amount required.
Ensure that all users are granted the least amount of privileges required to successfully operate.
Updates are available. Please see the references or vendor advisory for more information.
Daniel Beck, CloudBees, Inc, David Fiser of Trend Micro Nebula working with Trend Micro's Zero Day Initiative, Jesse Glick, CloudBees, Inc, Matt Sicker, CloudBees Inc, Oleg Nenashev, CloudBees, Inc, Viktor Gazdag NCC Group, Wadeck Follonier, Jesse Glick, and Daniel Beck, CloudBees, Inc
© 1995- Symantec Corporation
Permission to redistribute this alert electronically is granted as long as it is not edited in any way unless authorized by Symantec Security Response. Reprinting the whole or part of this alert in any medium other than electronically requires permission from firstname.lastname@example.org.
The information in the advisory is believed to be accurate at the time of publishing based on currently available information. Use of the information constitutes acceptance for use in an AS IS condition. There are no warranties with regard to this information. Neither the author nor the publisher accepts any liability for any direct, indirect, or consequential loss or damage arising from use of, or reliance on, this information.
Symantec, Symantec products, Symantec Security Response, and email@example.com are registered trademarks of Symantec Corp. and/or affiliated companies in the United States and other countries. All other registered and unregistered trademarks represented in this document are the sole property of their respective companies/owners.