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-2020-8237 (High) detected in json-bigint-0.3.1.tgz - autoclosed #82

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

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

CVE-2020-8237 - High Severity Vulnerability

Vulnerable Library - json-bigint-0.3.1.tgz

JSON.parse with bigints support

Library home page: https://registry.npmjs.org/json-bigint/-/json-bigint-0.3.1.tgz

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

Path to vulnerable library: stripe-distinct-usage-tracking/node_modules/json-bigint/package.json

Dependency Hierarchy: - firebase-admin-8.2.0.tgz (Root Library) - firestore-2.6.1.tgz - google-gax-1.15.3.tgz - google-auth-library-5.10.1.tgz - gcp-metadata-3.5.0.tgz - :x: **json-bigint-0.3.1.tgz** (Vulnerable Library)

Found in HEAD commit: ba1e42bf64eae15d92b539d654e321213e2d0b5b

Vulnerability Details

Prototype pollution in json-bigint npm package < 1.0.0 may lead to a denial-of-service (DoS) attack.

Publish Date: 2020-09-18

URL: CVE-2020-8237

CVSS 3 Score Details (7.5)

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

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: https://hackerone.com/reports/916430

Release Date: 2020-07-21

Fix Resolution: v1.0.0


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

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