Non-Constant Time String Comparison Affecting cookie-signature package, versions <1.0.4
Threat Intelligence
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk ID npm:cookie-signature:20160804
- published 29 Aug 2016
- disclosed 28 Jan 2014
- credit tenbits
Introduced: 28 Jan 2014
CVE-2016-1000236 Open this link in a new tabHow to fix?
Upgrade to 1.0.4 or greater.
Overview
'cookie-signature' is a library for signing cookies.
Versions before 1.0.4 of the library use the built-in string comparison mechanism, ===, and not a time constant string comparison. As a result, the comparison will fail faster when the first characters in the token are incorrect.
An attacker can use this difference to perform a timing attack, essentially allowing them to guess the secret one character at a time.
You can read more about timing attacks in Node.js on the Snyk blog: https://snyk.io/blog/node-js-timing-attack-ccc-ctf/