You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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. This issue arises from the manner in which the objects are initialized.
mend-for-github-combot
changed the title
CVE-2023-26136 (Critical) detected in tough-cookie-2.5.0.tgz
CVE-2023-26136 (Critical) detected in tough-cookie-3.0.1.tgz, tough-cookie-2.5.0.tgz
Mar 3, 2024
CVE-2023-26136 - Critical Severity Vulnerability
Vulnerable Libraries - tough-cookie-3.0.1.tgz, tough-cookie-2.5.0.tgz
tough-cookie-3.0.1.tgz
RFC6265 Cookies and Cookie Jar for node.js
Library home page: https://registry.npmjs.org/tough-cookie/-/tough-cookie-3.0.1.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/jsdom/node_modules/tough-cookie/package.json
Dependency Hierarchy:
tough-cookie-2.5.0.tgz
RFC6265 Cookies and Cookie Jar for node.js
Library home page: https://registry.npmjs.org/tough-cookie/-/tough-cookie-2.5.0.tgz
Path to dependency file: /package.json
Path to vulnerable library: /website/node_modules/tough-cookie/package.json
Dependency Hierarchy:
Found in HEAD commit: 67e433f207a0fc9c0fb2b8f7a2906f254c8c4b87
Found in base branch: master
Vulnerability Details
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. This issue arises from the manner in which the objects are initialized.
Publish Date: 2023-07-01
URL: CVE-2023-26136
CVSS 3 Score Details (9.8)
Base Score Metrics:
Suggested Fix
Type: Upgrade version
Origin: https://www.cve.org/CVERecord?id=CVE-2023-26136
Release Date: 2023-07-01
Fix Resolution (tough-cookie): 4.1.3
Direct dependency fix Resolution (jsdom): 16.6.0
The text was updated successfully, but these errors were encountered: