fetch-cookie-2.1.0.tgz: 1 vulnerabilities (highest severity is: 6.5) - autoclosed
mend-bolt-for-github opened this issue · 1 comments
Vulnerable Library - fetch-cookie-2.1.0.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/tough-cookie/package.json
Found in HEAD commit: 0b3d5216b45d4e39d3677092ffbeae66e09e0e4a
Vulnerabilities
CVE | Severity | CVSS | Dependency | Type | Fixed in (fetch-cookie version) | Remediation Available |
---|---|---|---|---|---|---|
CVE-2023-26136 | Medium | 6.5 | tough-cookie-4.1.2.tgz | Transitive | N/A* | ❌ |
*For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the "Details" section below to see if there is a version of transitive dependency where vulnerability is fixed.
Details
CVE-2023-26136
Vulnerable Library - tough-cookie-4.1.2.tgz
RFC6265 Cookies and Cookie Jar for node.js
Library home page: https://registry.npmjs.org/tough-cookie/-/tough-cookie-4.1.2.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/tough-cookie/package.json
Dependency Hierarchy:
- fetch-cookie-2.1.0.tgz (Root Library)
- ❌ tough-cookie-4.1.2.tgz (Vulnerable Library)
Found in HEAD commit: 0b3d5216b45d4e39d3677092ffbeae66e09e0e4a
Found in base branch: main
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 (6.5)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
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
Step up your Open Source Security Game with Mend here
✔️ This issue was automatically closed by Mend because the vulnerable library in the specific branch(es) was either marked as ignored or it is no longer part of the Mend inventory.