A research project inventorying RCE-by-design features and code execution risks in CI/CD pipeline tools.
Living Off the Pipeline (LOTP) is a supply chain security research project that inventories development tools commonly used in CI/CD pipelines to document their lesser-known RCE-by-design features and arbitrary code execution risks. It helps identify how these tools can be exploited when processing untrusted code changes or through workflow injection, addressing vulnerabilities in the software supply chain.
Security researchers, DevSecOps engineers, and development teams focused on securing CI/CD pipelines and understanding tool-level exploitation risks.
LOTP provides a centralized, community-driven resource for uncovering hidden security flaws in pipeline tools, inspired by projects like GTFOBins, offering practical insights for vulnerability assessment and mitigation in modern development workflows.
Supply Chain Security Research - Living Off The Pipeline tools
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
LOTP inventories development tools and documents their RCE-by-design features, providing a centralized reference for pipeline vulnerabilities, as emphasized in the README's focus on lesser-known exploitation risks.
Welcomes contributions via pull requests and issues, fostering collaborative threat discovery, inspired by projects like GTFOBins and LOLBAS for sustained updates.
Details how tools enable arbitrary code execution via workflow injection or untrusted code changes, offering actionable knowledge for real-world security assessments in CI/CD environments.
Released under Apache 2.0 and hosted on GitHub, making it freely available for security teams and researchers to use and contribute without restrictions.
LOTP is a catalog, not an active security tool; it lacks automated scanning, real-time monitoring, or integration capabilities, requiring manual consultation for risk assessment.
Relies on community submissions, so it may miss emerging tools or vulnerabilities, and updates are irregular, potentially leaving gaps in threat documentation.
Focuses on identifying risks rather than providing step-by-step fixes; the README doesn't extensively cover how to patch or prevent vulnerabilities, leaving implementation to users.