Pentesting Jenkins
Jenkins is an open-source automation server written in Java that helps developers build and test their software projects continuously. Similar to Tomcat.
Jenkins runs on Tomcat port 8080 by default. It also utilizes port 5000 to attach slave servers. This port is used to communicate between masters and slaves. Jenkins can use a local database, LDAP, Unix user database, delegate security to a servlet container, or use no authentication at all.
Version
It's usually in the footer section.
Command execution
Script Console
Once we have gained access to a Jenkins application, a quick way of achieving command execution on the underlying server is via the Script Console located under "Manage Jenkins" tab.
Web shell
Some snippet code that we could use:
Reverse shell
Some snippet code that we could use:
And have a listener in our attacking machine.
Windows
Invoke-PowerShellTcp.ps1
Against a Windows host, we could attempt to add a user and connect to the host via RDP or WinRM or, to avoid making a change to the system, use a PowerShell download cradle with Invoke-PowerShellTcp.ps1. We could run commands on a Windows-based Jenkins install using this snippet:
Java Reverse shell
Save this file, but modify first host and port.
Other RCEs
- CVE-2018-1999002 and CVE-2019-1003000 This flaw allows users with read permissions to bypass sandbox protections and execute code on the Jenkins master server. This exploit works against Jenkins version 2.137.
- Another vulnerability exists in Jenkins 2.150.2, which allows users with JOB creation and BUILD privileges to execute code on the system via Node.js. This vulnerability requires authentication, but if anonymous users are enabled, the exploit will succeed because these users have JOB creation and BUILD privileges by default.