CVE-2020-36049 (High) detected in socket.io-parser-3.3.0.tgz - autoclosed

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

CVE-2020-36049 - High Severity Vulnerability

Vulnerable Library - socket.io-parser-3.3.0.tgz

socket.io protocol parser

Library home page: https://registry.npmjs.org/socket.io-parser/-/socket.io-parser-3.3.0.tgz

Path to dependency file: portapps.github.io/package.json

Path to vulnerable library: portapps.github.io/node_modules/socket.io-parser

Dependency Hierarchy: - browser-sync-2.26.14.tgz (Root Library) - browser-sync-ui-2.26.14.tgz - socket.io-client-2.4.0.tgz - :x: **socket.io-parser-3.3.0.tgz** (Vulnerable Library)

Found in HEAD commit: 1be4cc7bd4c72e0c2a2f4d122df629bd32cae119

Found in base branch: dev

Vulnerability Details

socket.io-parser before 3.4.1 allows attackers to cause a denial of service (memory consumption) via a large packet because a concatenation approach is used.

Publish Date: 2021-01-08

URL: CVE-2020-36049

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://github.com/advisories/GHSA-xfhh-g9f5-x4m4

Release Date: 2021-01-08

Fix Resolution: socket.io-parser - 3.3.2,3.4.1

---

Step up your Open Source Security Game with WhiteSource here

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

:heavy_check_mark: 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.

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

:information_source: This issue was automatically re-opened by WhiteSource because the vulnerable library in the specific branch(es) has been detected in the WhiteSource inventory.

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

:heavy_check_mark: 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.