UnratednpmAmendedPublished
Timing Attack in csrf-lite
CVE-2016-10535 · GHSA-hjhr-r3gq-qvp6
- Affected
- npm csrf-lite < 0.1.2
- Fixed in
- 0.1.2· Vendor fix available
- Issue
- Affected versions of csrf-lite are vulnerable to timing attacks as a result of testing CSRF tokens via a fail-early comparison instead of a constant-time comparison. Timing attacks remove the exponential increase in entropy gained from increased secret length, by providing per-character feedback on the correctness of a guess via miniscule timing differences. Under favorable network conditions, an attacker can exploit this to guess the secret in no more than (1618)288 guesses, instead of the 16^18 guesses required were the timing attack not present. Recommendation Update to version 0.1.2 or later.
Recommended action: Upgrade to 0.1.2 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.