webpack-5.75.0.tgz: 1 vulnerabilities (highest severity is: 9.8) - autoclosed
Closed this issue · 1 comments
Vulnerable Library - webpack-5.75.0.tgz
Packs CommonJs/AMD modules for the browser. Allows to split your codebase into multiple bundles, which can be loaded on demand. Support loaders to preprocess files, i.e. json, jsx, es7, css, less, ... and your custom stuff.
Library home page: https://registry.npmjs.org/webpack/-/webpack-5.75.0.tgz
Path to dependency file: /frontend/package.json
Path to vulnerable library: /frontend/node_modules/webpack/package.json
Vulnerabilities
CVE | Severity | CVSS | Dependency | Type | Fixed in (webpack version) | Remediation Available |
---|---|---|---|---|---|---|
CVE-2023-28154 | Critical | 9.8 | webpack-5.75.0.tgz | Direct | 5.76.0 | ✅ |
Details
CVE-2023-28154
Vulnerable Library - webpack-5.75.0.tgz
Packs CommonJs/AMD modules for the browser. Allows to split your codebase into multiple bundles, which can be loaded on demand. Support loaders to preprocess files, i.e. json, jsx, es7, css, less, ... and your custom stuff.
Library home page: https://registry.npmjs.org/webpack/-/webpack-5.75.0.tgz
Path to dependency file: /frontend/package.json
Path to vulnerable library: /frontend/node_modules/webpack/package.json
Dependency Hierarchy:
- ❌ webpack-5.75.0.tgz (Vulnerable Library)
Found in base branch: main
Vulnerability Details
Webpack 5 before 5.76.0 does not avoid cross-realm object access. ImportParserPlugin.js mishandles the magic comment feature. An attacker who controls a property of an untrusted object can obtain access to the real global object.
Publish Date: 2023-03-13
URL: CVE-2023-28154
CVSS 3 Score Details (9.8)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
Suggested Fix
Type: Upgrade version
Release Date: 2023-03-13
Fix Resolution: 5.76.0
⛑️ Automatic Remediation is available for this issue
⛑️ Automatic Remediation is available 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.