TremiDkhar / fetch-github-profile

Fetch the GitHub profile of the user by username and pull the info from GitHub using GitHub API
https://fetch-github-profile.firebaseapp.com/
0 stars 0 forks source link

CVE-2021-23368 (Medium) detected in postcss-7.0.27.tgz - autoclosed #38

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

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

CVE-2021-23368 - Medium Severity Vulnerability

Vulnerable Library - postcss-7.0.27.tgz

Tool for transforming styles with JS plugins

Library home page: https://registry.npmjs.org/postcss/-/postcss-7.0.27.tgz

Path to dependency file: fetch-github-profile/package.json

Path to vulnerable library: fetch-github-profile/node_modules/postcss/package.json

Dependency Hierarchy: - parcel-bundler-1.12.5.tgz (Root Library) - :x: **postcss-7.0.27.tgz** (Vulnerable Library)

Found in HEAD commit: cbeee71a7c7f59c53517436979e0634d9b2a7174

Found in base branch: master

Vulnerability Details

The package postcss from 7.0.0 and before 8.2.10 are vulnerable to Regular Expression Denial of Service (ReDoS) during source map parsing.

Publish Date: 2021-04-12

URL: CVE-2021-23368

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

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23368

Release Date: 2021-04-12

Fix Resolution: postcss -8.2.10


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

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