CyberRota Analysis
AI-GeneratedThe vulnerability affects the Pipelines-as-Code feature in GitHub, where prior versions improperly validate the API host during webhook event processing. An unauthenticated attacker can exploit this flaw to send a locally signed GitHub App JWT to a malicious service, potentially allowing them to mint installation access tokens and gain unauthorized access based on the GitHub App's permissions. Organizations using affected versions should prioritize upgrading to the patched releases (0.37.8, 0.39.6, 0.42.1, or 0.48.0) to mitigate this security risk.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
Pipelines-as-Code is a CI/CD system that lets users define Tekton pipelines in source code repositories. Prior to 0.37.8, 0.39.6, 0.42.1, and 0.48.0, the GitHub App provider accepts X-GitHub-Enterprise-Host as the API host while processing webhook events containing an installation.id, before webhook signature validation or confirmation that the host matches the repository URL in the signed payload. An unauthenticated attacker who can reach the webhook endpoint can select an attacker-controlled host and cause the controller to send a locally signed GitHub App JWT to that service. The exposed JWT may be used to attempt to mint installation access tokens during its validity window, subject to the GitHub App installation and permissions. The incoming webhook installation-lookup path is also affected, but exploitation of that path requires the valid incoming webhook secret for the target Repository CR. This issue is fixed in versions 0.37.8, 0.39.6, 0.42.1, and 0.48.0.