billmcchesney1 / Hangar

Hackathon sponsorship made easy
MIT License
0 stars 0 forks source link

CVE-2021-32723 (Medium) detected in prismjs-1.21.0.tgz - autoclosed #29

Closed mend-for-github-com[bot] closed 4 months ago

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

CVE-2021-32723 - Medium Severity Vulnerability

Vulnerable Library - prismjs-1.21.0.tgz

Lightweight, robust, elegant syntax highlighting. A spin-off project from Dabblet.

Library home page: https://registry.npmjs.org/prismjs/-/prismjs-1.21.0.tgz

Path to dependency file: /package.json

Path to vulnerable library: /node_modules/prismjs/package.json

Dependency Hierarchy: - docsify-cli-4.4.1.tgz (Root Library) - docsify-4.11.6.tgz - :x: **prismjs-1.21.0.tgz** (Vulnerable Library)

Found in base branch: main

Vulnerability Details

Prism is a syntax highlighting library. Some languages before 1.24.0 are vulnerable to Regular Expression Denial of Service (ReDoS). When Prism is used to highlight untrusted (user-given) text, an attacker can craft a string that will take a very very long time to highlight. This problem has been fixed in Prism v1.24. As a workaround, do not use ASCIIDoc or ERB to highlight untrusted text. Other languages are not affected and can be used to highlight untrusted text.

Publish Date: 2021-06-28

URL: CVE-2021-32723

CVSS 3 Score Details (6.5)

Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: Required - 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://github.com/PrismJS/prism/security/advisories/GHSA-gj77-59wh-66hg

Release Date: 2021-06-28

Fix Resolution (prismjs): 1.24.0

Direct dependency fix Resolution (docsify-cli): 4.4.2


mend-for-github-com[bot] commented 4 months ago

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