Jenkins Developer Console Jenkins/2.401.3
endpoint /jenkins/script/ auth none
📋 Info Gathering
📁 File Read (Groovy)
💻 Shell Execution
🔬 Vulnerability Info

Vulnerability: Unauthenticated Script Console

Impact: RCE via Groovy script execution

CVE: CVE-2019-1003000 (Script Security)

Endpoint: /jenkins/script/

📖 Jenkins docs →

🔧 Jenkins Script Console — Unauthenticated Access

This is a simulation of a Jenkins 2.401.3 instance running with no authentication. The Script Console at /jenkins/script/ allows arbitrary Groovy script execution. Click any payload in the sidebar to load and execute a Groovy script.

✅ Info Gathering
📋
Enumerate plugins, version, system info
Reconnaissance phase
📁 File Read
📂
Read server files via Groovy File API
Path traversal
💻 RCE
⚡
Execute system commands via Groovy
Remote Code Execution
🖥️ Script Console
Type in an arbitrary Groovy script and execute it on the server. Useful for trouble-shooting and diagnostics. Use the println command to see the output.
All the classes from all the plugins are visible. jenkins.*, jenkins.model.*, hudson.*, and hudson.model.* are pre-imported.
1
🔓 How the Jenkins Script Console Vulnerability Works

Jenkins provides a Script Console at /jenkins/script/ that allows administrators to run arbitrary Groovy scripts for troubleshooting and diagnostics. When the instance is misconfigured without authentication, anyone can access this endpoint.

Groovy is a powerful JVM language that provides access to the underlying Java runtime:

  • new File("/etc/passwd").text — Read any file on the server
  • "whoami".execute().text — Execute arbitrary system commands
  • Jenkins.instance.pluginManager.plugins — Access internal Jenkins APIs

Impact: Complete server compromise — file read, RCE, credential theft, lateral movement.