search

uniquelyparticular / sync-moltin-to-shipengine

This Particular example demonstrates how you can sync paid/captured order status updates from Moltin to trigger emailing generated label from ShipEngine via Webhook API.
https://uniquelyparticular.com
MIT License
3 stars 3 forks source link

WS-2020-0127 (Medium) detected in npm-registry-fetch-4.0.2.tgz - autoclosed #392

Closed mend-bolt-for-github[bot] closed 2 years ago

mend-bolt-for-github[bot] commented 4 years ago

WS-2020-0127 - Medium Severity Vulnerability

Vulnerable Library - npm-registry-fetch-4.0.2.tgz

Fetch-based http client for use with npm registry APIs

Library home page: https://registry.npmjs.org/npm-registry-fetch/-/npm-registry-fetch-4.0.2.tgz

Path to dependency file: /package.json

Path to vulnerable library: /node_modules/npm/node_modules/npm-registry-fetch/package.json

Dependency Hierarchy: - semantic-release-15.14.0.tgz (Root Library) - npm-5.3.4.tgz - npm-6.13.4.tgz - :x: **npm-registry-fetch-4.0.2.tgz** (Vulnerable Library)

Found in HEAD commit: ec6fedd3023074a58c607fc8a2d1e04a4e2ab9c7

Found in base branch: master

Vulnerability Details

npm-registry-fetch before 4.0.5 and 8.1.1 is vulnerable to an information exposure vulnerability through log files.

Publish Date: 2020-07-07

URL: WS-2020-0127

CVSS 3 Score Details (5.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: None - Availability Impact: None

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: https://www.npmjs.com/advisories/1544

Release Date: 2020-07-07

Fix Resolution (npm-registry-fetch): 4.0.5

Direct dependency fix Resolution (semantic-release): 16.0.0-beta.1

Step up your Open Source Security Game with WhiteSource here

mend-bolt-for-github[bot] commented 2 years ago

:heavy_check_mark: This issue was automatically closed by WhiteSource because the vulnerable library in the specific branch(es) was either marked as ignored or it is no longer part of the WhiteSource inventory.