Trigger.dev: Account Takeover via Cross-Provider OAuth Email Matching in Google Login
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 | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Triggerdotdev | Trigger.dev |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.471% 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 is a platform for building and deploying fully managed AI agents and workflows. Prior to 4.5.2, addGoogleStrategy() in apps/webapp/app/services/googleAuth.server.ts passes a Google profile email to findOrCreateGoogleUser() in apps/webapp/app/models/user.server.ts without requiring Google's email_verified assertion. When existingEmailUser && !existingUser is true, the flow writes the new Google authIdentifier into the existing email-matched account and returns that user object, allowing an attacker-controlled Google profile with an unverified matching email to take over the account. This issue is fixed in version 4.5.2. | |
| Title | Trigger.dev: Account Takeover via Cross-Provider OAuth Email Matching in Google Login | |
| Weaknesses | CWE-287 | |
| References |
| |
| Metrics |
cvssV3_1
|