Trigger.dev: Prototype pollution via run metadata operations → process-wide cross-tenant DoS
21Vexday Risk Score
Sin señal de explotación. Ningún artefacto público de explotación conocido hasta ahora.
ssvc Trackcvss 8.5epss 0.4%
probabilidad de explotación
0.4%top 66% de las CVE
explotación observada
noninguna fuente lo reporta
Trigger.dev is a platform for building and deploying fully managed AI agents and workflows. From 3.3.8 until 4.5.6, the PUT /api/v1/runs/:runId/metadata endpoint passes attacker-controlled operation.key values to new JSONHeroPath(operation.key).set(newMetadata, value) in packages/core/src/v3/runMetadata/operations.ts without rejecting dangerous constructor and prototype path segments. A caller with a normal environment API key can pollute Object.prototype in the shared webapp process, corrupting Prisma queries and Prometheus labels, breaking other tenants' worker authentication, and causing a process-wide denial of service. This issue is fixed in version 4.5.6.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:H
Productos afectados
triggerdotdev · trigger.devReferencias
https://github.com/triggerdotdev/trigger.dev/commit/6997aeb05e27d2db47f9eda01fdc8a17c81a1ae0https://github.com/triggerdotdev/trigger.dev/pull/4316https://github.com/triggerdotdev/trigger.dev/releases/tag/v4.5.6https://github.com/triggerdotdev/trigger.dev/security/advisories/GHSA-p28v-f755-9qrg