pwn_jenkins
A collection of notes, scripts, and techniques for exploiting vulnerabilities and attacking Jenkins servers.
What is pwn_jenkins?
pwn_jenkins is a security research repository focused on attacking Jenkins automation servers. It documents critical vulnerabilities, provides exploitation scripts, and details post-compromise techniques for red teamers and penetration testers. The project serves as a practical guide for assessing and exploiting insecure Jenkins deployments.
Security researchers, penetration testers, and red team operators who need to audit or exploit Jenkins servers in authorized engagements.
It consolidates scattered Jenkins attack vectors into a single, actionable resource with working exploit code and scripts, saving time for security professionals during assessments.
Overview
Notes about attacking Jenkins servers
Use Cases
Best For
- Penetration testing Jenkins servers in corporate environments
- Exploiting specific CVEs like CVE-2024-23897 for arbitrary file reads
- Post-exploitation activities on compromised Jenkins instances
- Dumping and decrypting Jenkins credentials offline
- Learning offensive security techniques against CI/CD infrastructure
- Red team operations targeting automation servers
Not Ideal For
- Blue teams seeking detection rules and mitigation strategies for Jenkins attacks
- Jenkins administrators looking for security hardening guides or best practices
- Developers building secure Jenkins plugins without a focus on exploitation
- Educational courses on defensive security for CI/CD pipelines
Pros & Cons
Pros
Documents critical vulnerabilities like CVE-2024-23897 and CVE-2019-1003000 with detailed exploitation commands and scripts, saving research time.
Provides ready-to-use Python scripts for dumping build logs and decrypting secrets offline, as shown in the repository's scripts directory.
Includes Groovy scripts for command execution and reverse shells, with examples for automating attacks on specific slave nodes.
Emphasizes actionable code over theory, offering clear examples like memory dumping for LDAP credentials and password spraying techniques.
Cons
Purely offensive; lacks any mitigation strategies, patching advice, or security best practices for securing Jenkins servers.
Requires familiarity with penetration testing tools and Jenkins internals; not beginner-friendly, with minimal explanatory context.
Focuses on known CVEs up to a point; may not cover newer exploits or zero-days, and scripts might need updates for newer Jenkins versions.
Intended for authorized use only; unauthorized application could lead to legal issues, and the README offers no disclaimers on responsible usage.
Frequently Asked Questions
Found a gem we're missing?
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.