WS-2020-0208 (Medium) detected in highlight.js-10.3.1.tgz - autoclosed
Closed this issue · 1 comments
WS-2020-0208 - Medium Severity Vulnerability
Vulnerable Library - highlight.js-10.3.1.tgz
Syntax highlighting with language autodetection.
Library home page: https://registry.npmjs.org/highlight.js/-/highlight.js-10.3.1.tgz
Path to dependency file: Google-api-python-client/package.json
Path to vulnerable library: Google-api-python-client/node_modules/highlight.js/package.json
Dependency Hierarchy:
- render-content-5.2.0.tgz (Root Library)
- hubdown-2.6.0.tgz
- rehype-highlight-3.1.0.tgz
- lowlight-1.16.0.tgz
- ❌ highlight.js-10.3.1.tgz (Vulnerable Library)
- lowlight-1.16.0.tgz
- rehype-highlight-3.1.0.tgz
- hubdown-2.6.0.tgz
Found in HEAD commit: 4e6b7ecb9b39fc7d86c420ddb87c5c3712578339
Found in base branch: main
Vulnerability Details
If are you are using Highlight.js to highlight user-provided data you are possibly vulnerable. On the client-side (in a browser or Electron environment) risks could include lengthy freezes or crashes... On the server-side infinite freezes could occur... effectively preventing users from accessing your app or service (ie, Denial of Service). This is an issue with grammars shipped with the parser (and potentially 3rd party grammars also), not the parser itself. If you are using Highlight.js with any of the following grammars you are vulnerable. If you are using highlightAuto to detect the language (and have any of these grammars registered) you are vulnerable.
Publish Date: 2020-12-04
URL: WS-2020-0208
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: Low
- Integrity Impact: None
- Availability Impact: None
Suggested Fix
Type: Upgrade version
Origin: https://github.com/highlightjs/highlight.js/tree/10.4.1
Release Date: 2020-12-04
Fix Resolution: 10.4.1
Step up your Open Source Security Game with WhiteSource here
✔️ This issue was automatically closed by WhiteSource because the vulnerable library in the specific branch(es) was either marked as ignored or it is no longer part of the WhiteSource inventory.