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.
References
Link | Resource |
---|---|
https://github.com/denoland/deno/commit/0d1beed | Patch |
https://github.com/denoland/deno/commit/4f27d7cdc02e3edfb9d36275341fb8185d6e99ed | Patch |
https://github.com/denoland/deno/commit/a4003a5292bd0affefad3ecb24a8732886900f67 | Patch |
https://github.com/denoland/deno/security/advisories/GHSA-2x3r-hwv5-p32x | Exploit Vendor Advisory Patch |
https://github.com/denoland/deno/security/advisories/GHSA-2x3r-hwv5-p32x | Exploit Vendor Advisory Patch |
Configurations
History
09 Jun 2025, 15:11
Type | Values Removed | Values Added |
---|---|---|
CPE | cpe:2.3:a:deno:deno:*:*:*:*:*:*:*:* | |
First Time |
Deno deno
Deno |
|
References | () https://github.com/denoland/deno/commit/0d1beed - Patch | |
References | () https://github.com/denoland/deno/commit/4f27d7cdc02e3edfb9d36275341fb8185d6e99ed - Patch | |
References | () https://github.com/denoland/deno/commit/a4003a5292bd0affefad3ecb24a8732886900f67 - Patch | |
References | () https://github.com/denoland/deno/security/advisories/GHSA-2x3r-hwv5-p32x - Exploit, Vendor Advisory, Patch | |
CVSS |
v2 : v3 : |
v2 : unknown
v3 : 5.3 |
04 Jun 2025, 20:15
Type | Values Removed | Values Added |
---|---|---|
Summary | (en) 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. |
04 Jun 2025, 14:15
Type | Values Removed | Values Added |
---|---|---|
References | () https://github.com/denoland/deno/security/advisories/GHSA-2x3r-hwv5-p32x - | |
Summary |
|
03 Jun 2025, 23:15
Type | Values Removed | Values Added |
---|---|---|
New CVE |
Information
Published : 2025-06-03 23:15
Updated : 2025-06-09 15:11
NVD link : CVE-2025-24015
Mitre link : CVE-2025-24015
CVE.ORG link : CVE-2025-24015
JSON object : View
Products Affected
deno
- deno
CWE
CWE-347
Improper Verification of Cryptographic Signature