Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.
Open advisories
2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.
It is possible to bypass Deno's read/write permission checks by using ATTACH DATABASE statement. PoC
Recommended action: Upgrade to 0.134.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
This affects AES-256-GCM and AES-128-GCM in Deno, introduced by commit 0d1beed. Specifically, the authentication tag is not being validated. This means tampered ciphertexts or incorrect keys might not be detected, which breaks the guarantees expected from AES-GCM. Older versions of Deno correctly threw errors in such cases, as does Node.js. Without authentication tag verification, AES-GCM degrades to essentially CTR mode, removing integrity protection. Authenticated data set with setaad is also affected, as it is incorporated into the GCM hash (ghash) but this too is not validated, rendering AAD checks ineffective. PoC Impact While discovered through experimentation, authentication failures that should raise errors may be silently ignored.
Recommended action: Upgrade to 0.125.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.