Skip to content
Fencer Intel
medium 4.4

CVE-2016-1000236 json

cookie-signature Timing Attack

published 6y ago modified 4mo ago also GHSA-92vm-wfm5-mxvv , EUVD-2020-0260

cvss
4.4
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.9%
EPSS 0.9% chance of exploitation in 30 days, percentile 59%
public exploits
0
none known

Summary

Node-cookie-signature before 1.0.6 is affected by a timing attack due to the type of comparison used.

Patch / fix

  • npm cookie-signature 1.0.4
  • cookie-signature_project cookie-signature 1.0.6
  • node-cookie-signature Debian 14, Debian 13, Debian 12 1.1.0-1

debian advisories DEBIAN-CVE-2016-1000236

Is CVE-2016-1000236 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2016-1000236 updated cvss 5.4

nodejs-cookie-signature: Timing attack vulnerability

  • Red Hat OpenShift Enterprise 2 nodejs010-nodejs-cookie-signature
    affected: no fix planned “Will not fix”
  • Red Hat OpenShift Enterprise 3 nodejs-cookie-signature
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.90% chance of exploitation in the next 30 days, higher than 59% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 4.4 CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N
NVD 2.0 3.5 AV:N/AC:M/Au:S/C:P/I:N/A:N
GitHub 3.1 4.4 CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
npm cookie-signature
<1.0.4
1.0.4

Classification

Weakness
  • CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.