Jenkins plugins are prone to the following vulnerabilities: 1. Multiple information-disclosure vulnerabilities. 2. Multiple cross-site request forgery vulnerabilities. 3. Multiple HTML-injection vulnerabilities. 4. An XML External Entity injection 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: Alauda DevOps Pipeline Plugin through 2.3.2 Alauda Kubernetes Suport Plugin through 2.3.0 Build Failure Analyzer Plugin through 1.24.1 buildgraph-view Plugin through 1.8 Gerrit Trigger Plugin through 2.30.1 Mantis Plugin through 0.26 Maven Release Plug-in Plugin through 0.16.1 Mission Control Plugin through 0.9.16 Pipeline Aggregator View Plugin through 1.8 RapidDeploy Plugin through 4.1 Redgate SQL Change Automation Plugin through 2.0.3 Rundeck Plugin through 3.6.5 SCTMExecutor Plugin through 2.2 Spira Importer Plugin through 3.2.3 Team Concert Plugin through 1.3.0 WebSphere Deployer Plugin through 1.6.1 Weibo Plugin through 1.0.1
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.
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.