uniquelyparticular / sync-shipengine-to-zendesk

This Particular example demonstrates how you can sync shipping status from ShipEngine into Zendesk Sunshine via Webhook API.
https://uniquelyparticular.com
MIT License
1 stars 0 forks source link

WS-2019-0381 (Medium) detected in kind-of-6.0.2.tgz - autoclosed #75

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

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

WS-2019-0381 - Medium Severity Vulnerability

Vulnerable Library - kind-of-6.0.2.tgz

Get the native type of a value.

Library home page: https://registry.npmjs.org/kind-of/-/kind-of-6.0.2.tgz

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

Path to vulnerable library: /tmp/ws-scm/sync-shipengine-to-zendesk/node_modules/kind-of/package.json

Dependency Hierarchy: - micro-dev-3.0.0.tgz (Root Library) - chokidar-2.0.3.tgz - anymatch-2.0.0.tgz - micromatch-3.1.10.tgz - :x: **kind-of-6.0.2.tgz** (Vulnerable Library)

Found in HEAD commit: 7811aa9bdf5227fcea5e8724360ce4b62ff31b7b

Vulnerability Details

Versions of kind-of 6.x prior to 6.0.3 are vulnerable to a Validation Bypass. A maliciously crafted object can alter the result of the type check, allowing attackers to bypass the type checking validation.

Publish Date: 2019-12-30

URL: WS-2019-0381

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: None - Integrity Impact: Low - Availability Impact: None

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: https://github.com/jonschlinkert/kind-of/commit/975c13a7cfaf25d811475823824af3a9c04b0ba8

Release Date: 2020-03-18

Fix Resolution: kind-of - 6.0.3


Step up your Open Source Security Game with WhiteSource here

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

:information_source: This issue was automatically closed by WhiteSource because it is a duplicate of an existing issue: #76