sealed-env: TOTP secret embedded in unseal token payload (enterprise mode)
davidalmeidac sealed-env
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| sealed-env npm |
|
|
| io.github.davidalmeidac:sealed-env-core Maven |
|
|
davidalmeidac sealed-env
| Product | Affected | Fixed in |
|---|---|---|
| sealed-env npm |
|
|
| io.github.davidalmeidac:sealed-env-core Maven |
|
|
sealed-env is a cross-stack, zero-trust secret management library for Node.js and Java/Spring Boot. In sealed-env enterprise mode, versions 0.1.0-alpha.1 through 0.1.0-alpha.3 embedded the operator's literal TOTP secret in the JWS payload of every minted unseal token. JWS payload is base64-encoded JSON, NOT encrypted. Any party who could observe a minted token (CI build logs, container env dumps, kubectl describe pod, Sentry/Rollbar stack traces, log aggregators) could decode the payload and extract the TOTP secret in plaintext. This vulnerability is fixed in 0.1.0-alpha.4.
From the CVE record · GitHub_M
In sealed-env enterprise mode, affected versions embedded the operator’s literal TOTP secret in the base64-encoded, unencrypted JWS payload of every minted unseal token. Anyone who can observe a token, such as in logs or container environment dumps, can decode it and obtain the secret without further authentication or user interaction.
Teams running npm sealed-env or Maven io.github.davidalmeidac:sealed-env-core before 0.1.0-alpha.4 should check their installations.