GHSA-x3r2-fj3r-g5mv
CRITICALGHSA-x3r2-fj3r-g5mv is a critical-severity (CVSS 9.1) Information Exposure vulnerability in io.github.davidalmeidac:sealed-env-core. O3 Security confirms whether GHSA-x3r2-fj3r-g5mv is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
sealed-env: TOTP secret embedded in unseal token payload (enterprise mode)
Real-World Exposure
io.github.davidalmeidac:sealed-env-core📦sealed-envReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven, npm packages — download data is not available via public APIs for these ecosystems.
Description
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.
An attacker with (a) the master key (e.g. from a separate compromise such as a leaked CI secret) and (b) any single leaked unseal token can use the extracted TOTP secret to mint new valid unseal tokens for any future deploy indefinitely, breaking the second-factor property the library claimed.
Patched in 0.1.0-alpha.4 by replacing the embedded secret with a salt-bound HMAC derivative (enterprise_epoch = HMAC(totpSecret, salt || "epoch-v1")). The TOTP secret never leaves the operator's machine in the new design. The wire format change is incompatible — files sealed by affected versions must be re-sealed and the TOTP secret rotated. Full migration playbook in CHANGELOG.md.
Reported by an external reviewer who decoded the payload of a real minted token and confirmed bit-for-bit equality with the operator's .env.local TOTP secret.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | io.github.davidalmeidac:sealed-env-core | all versions | 0.1.0-alpha.4 |
| 📦npm | sealed-env | all versions | 0.1.0-alpha.4 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.github.davidalmeidac:sealed-env-core. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update io.github.davidalmeidac:sealed-env-core to 0.1.0-alpha.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-x3r2-fj3r-g5mv is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-x3r2-fj3r-g5mv is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-x3r2-fj3r-g5mv. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-x3r2-fj3r-g5mv in your dependencies?
O3 detects GHSA-x3r2-fj3r-g5mv across Maven, npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.