deno is vulnerable to Observable Timing Discrepancy
20
Low Risk
The Node compatibility AES-GCM decrypt path compared the authentication tag with a plain equality check that can short-circuit on the first differing byte, leaking timing differences to an observer. An attacker who can repeatedly trigger AES-GCM decrypt and measure timing may narrow in on the expected tag. The fix compares the tag using a constant-time comparison so the check does not vary with byte-wise matches.
You are affected if you are using a version that falls within the vulnerable range.
deno is vulnerable to Observable Timing Discrepancy in versions 0.0.1 - 2.7.6.
Upgrade the deno library to the patch version.
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

SOC 2Compliant
ISO 27001Compliant