Tough-cookie is a cookie parsing and management library. Versions 0.9.7 through 2.2.2 contain a vulnerable regular expression that, under certain conditions involving long strings of semicolons in the "Cookie" header, causes the event loop to block for excessive amounts of time. External References: https://nodesecurity.io/advisories/130 Upstream fixes: https://github.com/SalesforceEng/tough-cookie/commit/e4fc2e0f9ee1b7a818d68f0ac7ea696f377b1534 https://github.com/SalesforceEng/tough-cookie/commit/615627206357d997d5e6ff9da158997de05235ae
Created nodejs-tough-cookie tracking bugs for this issue: Affects: fedora-all [bug 1359819]
nodejs-tough-cookie-2.3.1-1.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.
If tough-cookie module is used to parse Cookie header value, this flaw could cause it to use excessive amount of CPU time (cookie header takes long to parse). The actual impact depends on the maximum value length that can be received by the application. If node.js is deployed behind a web server such as Apache httpd or nginx, default header size limits of those servers (4-8K): http://stackoverflow.com/questions/686217/maximum-on-http-header-values#8623061 greatly mitigate impact of this issue. node.js directly expose to the internet can process larger headers, and hence possible impact is higher.
This issue has been addressed in the following products: Red Hat OpenShift Container Platform 3.3 Red Hat OpenShift Enterprise 3.2 Red Hat OpenShift Enterprise 3.1 Via RHSA-2016:2101 https://access.redhat.com/errata/RHSA-2016:2101
This issue has been addressed in the following products: Red Hat Software Collections for Red Hat Enterprise Linux 6 Red Hat Software Collections for Red Hat Enterprise Linux 6.7 EUS Red Hat Software Collections for Red Hat Enterprise Linux 7 Red Hat Software Collections for Red Hat Enterprise Linux 7.3 EUS Via RHSA-2017:2912 https://access.redhat.com/errata/RHSA-2017:2912