Tough-Cookie vulnerabilitiesRanked by how likely they are to be used.
Tough-Cookie is made by Salesforce. We track 3 published vulnerabilities in it, across 42 versions. None of them is on the list of flaws known to be exploited today. If you run Tough-Cookie, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Tough-Cookie vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Tough-Cookie's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Tough-Cookie flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 3.3%CVE-2017-15010High
A ReDoS (regular expression denial of service) flaw was found in the tough-cookie module before 2.3.3 for Node.js.
- 2.6%CVE-2023-26136Critical
Versions of the package tough-cookie before 4.1.3 are vulnerable to Prototype Pollution due to improper handling of Cookies when using CookieJar in rejectPublicSuffixes=false mode.
- 2.4%CVE-2016-1000232Medium
NodeJS Tough-Cookie version 2.2.2 contains a Regular Expression Parsing vulnerability in HTTP request Cookie Header parsing that can result in Denial of Service.
Running Tough-Cookie? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
A ReDoS (regular expression denial of service) flaw was found in the tough-cookie module before 2.3.3 for Node.js. An attacker that is able to make an HTTP request using a specially crafted cookie may cause the application to consume an excessive amount of CPU.
- Matched to
- Tough-Cookie on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 3 published vulnerabilities listed under the name Tough-Cookie, across 42 versions.
None of Tough-Cookie's vulnerabilities is on the list of flaws known to be exploited today.
Create a EdgeProtect account and track Tough-Cookie. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.