Trigger.dev before 4.5.6 Authentication Bypass via Hardcoded Default Secrets
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| triggerdotdev | trigger.dev | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Triggerdotdev | Trigger.dev |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.512% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Triggerdotdev
Triggerdotdev trigger.dev |
|
| Vendors & Products |
Triggerdotdev
Triggerdotdev trigger.dev |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Trigger.dev before 4.5.6 self-hosted Docker Compose deployments using the default secrets from hosting/docker/.env.example allow authentication bypass because the hardcoded MAGIC_LINK_SECRET lets anyone forge valid magic link tokens. Unauthenticated attackers can log in as any email address, then reach Postgres, Redis, and ClickHouse with default credentials from runner containers on infrastructure networks, compromising all tenant data. | |
| Title | Trigger.dev before 4.5.6 Authentication Bypass via Hardcoded Default Secrets | |
| Weaknesses | CWE-653 | |
| References |
| |
| Metrics |
cvssV3_1
|