CVE-2021-23362 (Medium) detected in hosted-git-info-2.7.1.tgz - autoclosed

[mend-bolt-for-github[bot]]

CVE-2021-23362 - Medium Severity Vulnerability

Vulnerable Library - hosted-git-info-2.7.1.tgz

Provides metadata and conversions from repository urls for Github, Bitbucket and Gitlab

Library home page: https://registry.npmjs.org/hosted-git-info/-/hosted-git-info-2.7.1.tgz

Path to dependency file: serverless-oauth/package.json

Path to vulnerable library: serverless-oauth/node_modules/hosted-git-info

Dependency Hierarchy: - semantic-release-15.13.14.tgz (Root Library) - :x: **hosted-git-info-2.7.1.tgz** (Vulnerable Library)

Found in HEAD commit: e45ef645b834c42d08442b44219ebe3f718e535e

Vulnerability Details

The package hosted-git-info before 3.0.8 are vulnerable to Regular Expression Denial of Service (ReDoS) via regular expression shortcutMatch in the fromUrl function in index.js. The affected regular expression exhibits polynomial worst-case time complexity.

Publish Date: 2021-03-23

URL: CVE-2021-23362

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://github.com/npm/hosted-git-info/releases/tag/v3.0.8

Release Date: 2021-03-23

Fix Resolution: hosted-git-info - 3.0.8

---

Step up your Open Source Security Game with WhiteSource here

[mend-bolt-for-github[bot]]

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

[mend-bolt-for-github[bot]]

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

[mend-bolt-for-github[bot]]

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