WS-2023-0004 (High) detected in jszip-3.4.0.tgz, jszip-3.5.0.tgz - autoclosed

[mend-for-github-com]

WS-2023-0004 - High Severity Vulnerability

Vulnerable Libraries - jszip-3.4.0.tgz, jszip-3.5.0.tgz

jszip-3.4.0.tgz

Create, read and edit .zip files with JavaScript http://stuartk.com/jszip

Library home page: https://registry.npmjs.org/jszip/-/jszip-3.4.0.tgz

Path to dependency file: /package.json

Path to vulnerable library: /node_modules/snyk-nuget-plugin/node_modules/jszip/package.json

Dependency Hierarchy:

• snyk-1.406.0.tgz (Root Library)
  • snyk-nuget-plugin-1.19.3.tgz
    • ❌ jszip-3.4.0.tgz (Vulnerable Library)

jszip-3.5.0.tgz

Create, read and edit .zip files with JavaScript http://stuartk.com/jszip

Library home page: https://registry.npmjs.org/jszip/-/jszip-3.5.0.tgz

Path to dependency file: /package.json

Path to vulnerable library: /node_modules/jszip/package.json

Dependency Hierarchy:

• snyk-1.406.0.tgz (Root Library)
  • snyk-gradle-plugin-3.7.0.tgz
    • java-call-graph-builder-1.14.0.tgz
      • ❌ jszip-3.5.0.tgz (Vulnerable Library)

Found in HEAD commit: 2e9d597fe70064b9c61d9203c8a93a380a667238

Found in base branch: master

Vulnerability Details

jszip before 3.8.0 does not sanitize filenames when files are loaded with loadAsync, which makes the library vunerable to zip-slip attack.

Publish Date: 2023-01-04

URL: WS-2023-0004

CVSS 3 Score Details (7.3)

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: Low

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Release Date: 2023-01-04

Fix Resolution (jszip): 3.6.0

Direct dependency fix Resolution (snyk): 1.667.0

Fix Resolution (jszip): 3.6.0

Direct dependency fix Resolution (snyk): 1.667.0

---

⛑️ Automatic Remediation is available for this issue

[mend-for-github-com]

✔️ 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.