Description
Trigger.dev versions before 4.5.2 fail to validate environment membership during run replay operations, allowing authenticated attackers to inject task runs into arbitrary environments. Attackers can replay their own runs into other organizations' or projects' environments to consume victim resources and pollute run history.
Affected products
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| triggerdotdev | trigger.dev | < 4.5.2 | 4.5.2 |
Affected packages
| Ecosystem | Package | Affected | Fixed | Record |
|---|---|---|---|---|
| npm | trigger.dev | < 4.5.2 | 4.5.2 | GHSA-qxpp-qjg8-x4jv |
References
- GitHub Issue #4173 issue-tracking
- https://github.com/triggerdotdev/trigger.dev product
- https://github.com/triggerdotdev/trigger.dev/commit/34b1a181c2a1d33a53ebab88f84b05f81fea4254 patch
- Trigger.dev v4.5.2 Release Notes release-notes
- GitHub Security Advisory (GHSA-qxpp-qjg8-x4jv) vendor-advisory
- VulnCheck Advisory: Trigger.dev before 4.5.2 Unauthorized Environment Access via Run Replay third-party-advisory