Описание
Deno's AES GCM authentication tags are not verified
Summary
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 set_aad 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.
Ссылки
- https://github.com/denoland/deno/security/advisories/GHSA-2x3r-hwv5-p32x
- https://nvd.nist.gov/vuln/detail/CVE-2025-24015
- https://github.com/denoland/deno/commit/0d1beed
- https://github.com/denoland/deno/commit/0d1beed2e3633d71d5e288e0382b85be361ec13d
- https://github.com/denoland/deno/commit/4f27d7cdc02e3edfb9d36275341fb8185d6e99ed
- https://github.com/denoland/deno/commit/a4003a5292bd0affefad3ecb24a8732886900f67
Пакеты
deno
>= 1.46.0, < 2.1.7
2.1.7
deno_node
>= 0.102.0, < 0.125.0
0.125.0
Связанные уязвимости
Deno is a JavaScript, TypeScript, and WebAssembly runtime. Versions 1.46.0 through 2.1.6 have an issue that affects AES-256-GCM and AES-128-GCM in Deno in which 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 set_aad is also affected, as it is incorporated into the GCM hash (ghash) but this too is not validated, rendering AAD checks ineffective. Version 2.1.7 includes a patch that addresses this issue.