[Trend]Jenkins Admins: Relying on Default Settings Could Put Master at Risk of Remote Code Execution Attacks

[igor51]

Jenkins Admins: Relying on Default Settings Could Put Master at Risk of Remote Code Execution Attacks

In our analysis, we observed that a user account with less privilege can gain administrator rights over the automation server if jobs are built on the master machine (i.e., the main Jenkins server), a setup enabled by default. An exploit for this can be easily written using shell spawn — a default build step. If an exploit is successfully deployed, an attacker can perform remote code execution (RCE) on the master, which can result to Jenkins being completely overwritten.

The post Jenkins Admins: Relying on Default Settings Could Put Master at Risk of Remote Code Execution Attacks appeared first on .

Source: Jenkins Admins: Relying on Default Settings Could Put Master at Risk of Remote Code Execution Attacks