Trigger.dev
Trigger.dev before 4.5.0 Missing Authentication in Dashboard Run Replay Action
Trigger.dev before 4.5.0 performs no authentication or organization check in the action handler of the dashboard run replay route (resources.taskruns.$runParam.replay) and looks up the run by friendlyId alone. A remote attacker who knows a victim's run friendlyId can replay it into an environment of their choosing, exposing the victim's task payload or running the task again with the victim's secrets.
First public PoC
None yetno public PoC found
Public PoCs00 on GitHub
CVSS8.3high · scored by CNA · CWE-306
CISA KEV
Not listednot known exploited
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
triggerdotdev trigger.dev
- < 4.5.0
Fixed in 4.5.0
Mitigation
Upgrade trigger.dev to 4.5.0 or later.
References
- Vendor advisory github.com/triggerdotdev/trigger.dev/security/…
- Vendor advisory github.com/triggerdotdev/trigger.dev/security/…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.