Trigger.dev before 4.5.2 Server-Side Request Forgery via webhook alert-channel
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.348% 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.2 contains a server-side request forgery vulnerability in webhook alert channel delivery URLs that are fetched without validation or SSRF protection. Authenticated users with organization membership can create alert channels with URLs targeting internal services and metadata endpoints, allowing the server to issue POST requests to restricted resources. | |
| Title | Trigger.dev before 4.5.2 Server-Side Request Forgery via webhook alert-channel | |
| Weaknesses | CWE-918 | |
| References |
|
|
| Metrics |
cvssV3_1
|