Multiple Jenkins Plugins Multiple Security Vulnerabilities



Date Discovered

October 23, 2019


Jenkins plugins are prone to the following vulnerabilities: 1. Multiple information disclosure vulnerabilities. 2. Multiple cross-site request forgery vulnerabilities. 3. A security-bypass vulnerabilities. 4. An XML External Entity injection vulnerability 5. A cross-site scripting vulnerability. 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 are affected: 360 FireLine plugin version 1.7.2 and prior are vulnerable Bitbucket OAuth plugin version 0.9 and prior are vulnerable build-metrics plugin version 1.3 and prior are vulnerable Deploy WebLogic plugin version 4.1 and prior are vulnerable Dynatrace Application Monitoring plugin version 2.1.3 and 2.1.4 and prior are vulnerable ElasticBox Jenkins Kubernetes CI/CD plugin version 1.3 and prior are vulnerable Global Post Script plugin version 1.1.4 and prior are vulnerable Libvirt Slaves plugin version 1.8.5 and prior are vulnerable Mattermost Notification plugin version 2.7.0 and prior are vulnerable Sonar Gerrit plugin version 2.3 and prior are vulnerable Zulip plugin version 1.1.0 and prior are vulnerable

Technologies Affected

  • Jenkins 360 FireLine 1.7.0
  • Jenkins 360 FireLine 1.7.2
  • Jenkins Bitbucket OAuth 0.9
  • Jenkins Deploy WebLogic 4.1
  • Jenkins Dynatrace Application Monitoring 2.1.3
  • Jenkins Dynatrace Application Monitoring 2.1.4
  • Jenkins ElasticBox Kubernetes CI/CD 1.3
  • Jenkins Global Post Script 1.1.4
  • Jenkins Libvirt Slaves 1.8.5
  • Jenkins Mattermost Notification 2.6.2
  • Jenkins Mattermost Notification 2.6.3
  • Jenkins Mattermost Notification 2.7.0
  • Jenkins Sonar Gerrit 2.3
  • Jenkins Zulip 1.1.0
  • Jenkins build-metrics 1.3


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.

Set web browser security to disable the execution of JavaScript.
Since a successful exploit of these issues allows malicious script code to execute in web clients, consider disabling support for script code and active content within a client browser. Note that this mitigation tactic might adversely affect legitimate websites that rely on the execution of browser-based script code.

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.


James Holderness, IB Boost, Oleg Nenashev, CloudBees, Inc, Thomas de Grenier de Latour, Viktor Gazdag NCC Group and Wasin Saengow

© 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


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 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.