uniquelyparticular / stripe-distinct-usage-tracking

This Particular example demonstrates how you can track unique Usage Records for Metered Pricing Subscriptions in Stripe.
https://uniquelyparticular.com
MIT License
1 stars 1 forks source link

CVE-2021-23337 (High) detected in lodash-4.17.14.tgz - autoclosed #137

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

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

CVE-2021-23337 - High Severity Vulnerability

Vulnerable Library - lodash-4.17.14.tgz

Lodash modular utilities.

Library home page: https://registry.npmjs.org/lodash/-/lodash-4.17.14.tgz

Path to dependency file: stripe-distinct-usage-tracking/package.json

Path to vulnerable library: stripe-distinct-usage-tracking/node_modules/lodash

Dependency Hierarchy: - firebase-admin-8.2.0.tgz (Root Library) - storage-2.5.0.tgz - async-2.6.2.tgz - :x: **lodash-4.17.14.tgz** (Vulnerable Library)

Found in HEAD commit: 288b1c7d0d0acd2be479cdcac3dd10a64fc6e714

Vulnerability Details

Lodash versions prior to 4.17.21 are vulnerable to Command Injection via the template function.

Publish Date: 2021-02-15

URL: CVE-2021-23337

CVSS 3 Score Details (7.2)

Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: High - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: High - Availability Impact: High

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: https://github.com/lodash/lodash/commit/3469357cff396a26c363f8c1b5a91dde28ba4b1c

Release Date: 2021-02-15

Fix Resolution: lodash - 4.17.21


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: #142

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: #142