Trigger.dev before 4.6.0 fails to verify that an authenticated user controls a GitHub App installation before binding it to their organization. Attackers can claim another user's GitHub App installation by replaying state cookies and supplying sequential installation identifiers, gaining unauthorized access to the victim's repositories.
Attack Parameters
Attack Vector
Network
Can be exploited remotely
Attack Complexity
High
Difficult to exploit
Attack Requirements
Present
Additional conditions required
Privileges Required
Low
Basic privileges needed
User Interaction
None
No user interaction needed
Impact Assessment
Confidentiality
High
Complete data leak
Integrity
Low
Partial data modification
Availability
None
No disruption
CVSS Vector v4.0
Weakness Type (CWE)
Vulnerable Products
triggerdotdev:trigger.dev
References 5
https://github.com/triggerdotdev/trigger.dev
disclosure@vulncheck.com
https://github.com/triggerdotdev/trigger.dev/blob/v4.5.16/apps/webapp/app/servi…
disclosure@vulncheck.com
https://github.com/triggerdotdev/trigger.dev/blob/v4.6.0/apps/webapp/app/servic…
disclosure@vulncheck.com
https://github.com/triggerdotdev/trigger.dev/security/advisories/GHSA-9rx3-j5hm…
disclosure@vulncheck.com
https://www.vulncheck.com/advisories/trigger-dev-before-4.6.0-github-app-instal…
disclosure@vulncheck.com