axios-0.1.0.tgz: 1 vulnerabilities (highest severity is: 6.5) - autoclosed
mend-for-github-com opened this issue · comments
Vulnerable Library - axios-0.1.0.tgz
Path to dependency file: /nestjs-exchange-rates/package.json
Path to vulnerable library: /nestjs-exchange-rates/node_modules/axios/package.json
Found in HEAD commit: 3b9bae980eb794fab08e5addef96e9ace5acb327
Vulnerabilities
CVE | Severity | CVSS | Dependency | Type | Fixed in (axios version) | Remediation Possible** |
---|---|---|---|---|---|---|
CVE-2023-45857 | Medium | 6.5 | axios-0.27.2.tgz | Transitive | 2.0.0 | ✅ |
**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation
Details
CVE-2023-45857
Vulnerable Library - axios-0.27.2.tgz
Promise based HTTP client for the browser and node.js
Library home page: https://registry.npmjs.org/axios/-/axios-0.27.2.tgz
Path to dependency file: /nestjs-exchange-rates/package.json
Path to vulnerable library: /nestjs-exchange-rates/node_modules/axios/package.json
Dependency Hierarchy:
- axios-0.1.0.tgz (Root Library)
- ❌ axios-0.27.2.tgz (Vulnerable Library)
Found in HEAD commit: 3b9bae980eb794fab08e5addef96e9ace5acb327
Found in base branch: main
Vulnerability Details
An issue discovered in Axios 1.5.1 inadvertently reveals the confidential XSRF-TOKEN stored in cookies by including it in the HTTP header X-XSRF-TOKEN for every request made to any host allowing attackers to view sensitive information.
Publish Date: 2023-11-08
URL: CVE-2023-45857
CVSS 3 Score Details (6.5)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
Suggested Fix
Type: Upgrade version
Release Date: 2023-11-08
Fix Resolution (axios): 1.6.0
Direct dependency fix Resolution (@nestjs/axios): 2.0.0
⛑️ Automatic Remediation will be attempted for this issue.
⛑️Automatic Remediation will be attempted for this issue.
✔️ 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.