GHSA-7J2R-JRX9-GQWX
ToolJet Helm chart hard codes the JWT and encryption keys
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Divulgación | Publicada | GHSA-7J2R-JRX9-GQWX divulgada | |
| Monitoreo | Detectada | Ingresó al índice | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
Summary
The official Helm chart hard codes `0123456789ABCDEF` as both `secret_key_base`, the JWT HMAC signing secret, and `lockbox_key`, the AES-256-GCM data encryption master key, with no runtime validation. ToolJet's Docker and EC2 paths correctly auto generate this value, so the Helm chart is the outlier.
Details
`deploy/helm/values.yaml:26-27` supplies both values as literals. Nothing validates them at startup.
PoC
Deploy ToolJet via the official Helm chart without overriding `values.yaml`, which is the default path.
- `node forge.js`
- The script signs a session token with the published key and confirms the application's verification accepts it.
- The same key decrypts stored datasource credentials, since it doubles as the encryption master key.
A patched chart has no default, requiring the operator to supply a value or generating one into a Secret at install, and the application refuses to start when the value matches a shipped default.
I can send the complete run output on request.
Impact
Anyone who can reach a Helm deployed instance forges a session token for any user, and can decrypt every stored datasource credential, because the encryption master key is the same published constant.
Suggested remediation
- Remove the default from `values.yaml` and require an operator supplied value, or generate into a Secret at install time.
- Refuse to start when the value matches the shipped default or is shorter than 32 bytes, matching the behaviour the Docker path already implements.
Disclosure
I can attach the proof of concept and the raw output if that is useful. Nothing will be disclosed publicly until you have patched and published.
Audited at commit `072e2ee`.
Incluye detalles técnicos publicados por el investigador. Úselos solo para validar y corregir sus propios sistemas.
Rangos afectados
Estado del parche por paquete
| Paquete / producto | Estado | Corregida en | Desde divulgación | Última versión |
|---|---|---|---|---|
npmtooljet |
Sin parche | — | — | 0.0.1-security.1 afectada |
Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
https://github.com/ToolJet/ToolJet/security/advisories/GHSA-7j2r-jrx9-gqwxLas referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
