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-0068 (Medium) detected in multiple libraries - autoclosed #332

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

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

WS-2020-0068 - Medium Severity Vulnerability

Vulnerable Libraries - yargs-parser-10.1.0.tgz, yargs-parser-9.0.2.tgz, yargs-parser-13.1.1.tgz, yargs-parser-16.1.0.tgz

yargs-parser-10.1.0.tgz

the mighty option parser used by yargs

Library home page: https://registry.npmjs.org/yargs-parser/-/yargs-parser-10.1.0.tgz

Path to dependency file: /tmp/ws-scm/sync-moltin-to-shipengine/package.json

Path to vulnerable library: /tmp/ws-scm/sync-moltin-to-shipengine/node_modules/ts-jest/node_modules/yargs-parser/package.json

Dependency Hierarchy: - semantic-release-15.14.0.tgz (Root Library) - commit-analyzer-6.3.3.tgz - conventional-commits-parser-3.0.8.tgz - meow-5.0.0.tgz - :x: **yargs-parser-10.1.0.tgz** (Vulnerable Library)

yargs-parser-9.0.2.tgz

the mighty option parser used by yargs

Library home page: https://registry.npmjs.org/yargs-parser/-/yargs-parser-9.0.2.tgz

Path to dependency file: /tmp/ws-scm/sync-moltin-to-shipengine/package.json

Path to vulnerable library: /tmp/ws-scm/sync-moltin-to-shipengine/node_modules/jsome/node_modules/yargs-parser/package.json

Dependency Hierarchy: - micro-dev-3.0.0.tgz (Root Library) - jsome-2.5.0.tgz - yargs-11.1.0.tgz - :x: **yargs-parser-9.0.2.tgz** (Vulnerable Library)

yargs-parser-13.1.1.tgz

the mighty option parser used by yargs

Library home page: https://registry.npmjs.org/yargs-parser/-/yargs-parser-13.1.1.tgz

Path to dependency file: /tmp/ws-scm/sync-moltin-to-shipengine/package.json

Path to vulnerable library: /tmp/ws-scm/sync-moltin-to-shipengine/node_modules/yargs-parser/package.json

Dependency Hierarchy: - jest-24.9.0.tgz (Root Library) - jest-cli-24.9.0.tgz - yargs-13.3.0.tgz - :x: **yargs-parser-13.1.1.tgz** (Vulnerable Library)

yargs-parser-16.1.0.tgz

the mighty option parser used by yargs

Library home page: https://registry.npmjs.org/yargs-parser/-/yargs-parser-16.1.0.tgz

Path to dependency file: /tmp/ws-scm/sync-moltin-to-shipengine/package.json

Path to vulnerable library: /tmp/ws-scm/sync-moltin-to-shipengine/node_modules/semantic-release/node_modules/yargs-parser/package.json

Dependency Hierarchy: - semantic-release-15.14.0.tgz (Root Library) - yargs-15.0.2.tgz - :x: **yargs-parser-16.1.0.tgz** (Vulnerable Library)

Found in HEAD commit: d66c99a0c5b66580d24572646c2d7f6068ed184a

Vulnerability Details

Affected versions of yargs-parser are vulnerable to prototype pollution. Arguments are not properly sanitized, allowing an attacker to modify the prototype of Object, causing the addition or modification of an existing property that will exist on all objects. Parsing the argument --foo.__proto__.bar baz' adds a bar property with value baz to all objects. This is only exploitable if attackers have control over the arguments being passed to yargs-parser.

Publish Date: 2020-05-01

URL: WS-2020-0068

CVSS 3 Score Details (5.5)

Base Score Metrics: - Exploitability Metrics: - Attack Vector: N/A - Attack Complexity: N/A - Privileges Required: N/A - User Interaction: N/A - Scope: N/A - Impact Metrics: - Confidentiality Impact: N/A - Integrity Impact: N/A - Availability Impact: N/A

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: https://www.npmjs.com/package/yargs-parser

Release Date: 2020-05-04

Fix Resolution: https://www.npmjs.com/package/yargs-parser/v/18.1.2,https://www.npmjs.com/package/yargs-parser/v/15.0.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.