Bug 1918266 (CVE-2020-36049)

Summary: CVE-2020-36049 yarnpkg-socket.io-parser: a denial of service (memory consumption) via a large packet because a concatenation approach is used
Product: [Other] Security Response Reporter: Marian Rehak <mrehak>
Component: vulnerabilityAssignee: Red Hat Product Security <security-response-team>
Status: CLOSED WONTFIX QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: unspecifiedCC: amackenz, amasferr, bdettelb, chazlett, drieden, mcooper, mkudlej, tjochec, tomckay
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: socket.io-parser 3.4.1 Doc Type: If docs needed, set a value
Doc Text:
An uncontrolled resource consumption vulnerability was found in socket.io-parser. If an attacker crafts a packet with a very large payload length, this can cause the parser to consume an ever-increasing amount of memory, resulting in a denial of service. The highest threat from this vulnerability is to system availability.
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-10-28 01:44:23 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1918267, 1997390    

Description Marian Rehak 2021-01-20 11:08:01 UTC
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.

Reference:

https://github.com/bcaller/kill-engine-io
https://github.com/socketio/socket.io-parser/commit/dcb942d24db97162ad16a67c2a0cf30875342d55

Comment 1 Mark Cooper 2021-01-27 07:51:43 UTC
External References:

https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-1056753

Comment 2 Mark Cooper 2021-01-27 07:54:58 UTC
Similar to CVE-2020-36048, i think this should have an Important impact as it's primary use is to decode packets as part of the socket.io library. So again, results in a remote DoS. 

However again leaving Quay affects as Low, as these look like dev dependencies to me but want to confirm with engineering. 

$ npm list --prod | grep socket