CVE-2025-24015
- Source
- https://cve.org/CVERecord?id=CVE-2025-24015
- Import Source
- https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-24015.json
- JSON Data
- https://api.osv.dev/v1/vulns/CVE-2025-24015
- Aliases
- Downstream
- Published
- 2025-06-03T22:48:52.906Z
- Modified
- 2026-04-10T05:22:54.823917Z
- Severity
-
- 7.7 (High) CVSS_V4 - CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:P CVSS Calculator
- Summary
- Deno's AES GCM authentication tags are not verified
- Details
-
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.
- Database specific
{ "cwe_ids": [ "CWE-347" ], "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/24xxx/CVE-2025-24015.json", "cna_assigner": "GitHub_M" }- References
-
- https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/24xxx/CVE-2025-24015.json
- 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/4f27d7cdc02e3edfb9d36275341fb8185d6e99ed
- https://github.com/denoland/deno/commit/a4003a5292bd0affefad3ecb24a8732886900f67