ChainSocket.io-Parsernpm:socket.io-parser
Socket.io-Parser: successive fixes (2020–2023)
3 CVEs over 3 generations, 7 Jan 2021 to 27 May 2023.
Family tree
Left to right by publication date.Oldest first. Select a CVE to open it.- CVE-2020-360497 Jan 2021 First in the chain
- CVE-2022-242125 Oct 2022 related to CVE-2020-36049
- CVE-2023-3269527 May 2023 related to CVE-2022-2421related to CVE-2020-36049
Exploited in the wild (CISA KEV) Not in KEV Priority score (0 to 100) High confidence Medium Low Link confidenceHow strong the evidence is that two CVEs are related. High: stated in the CVE text or linked in an advisory, or the same code was patched one release apart. Medium: the same code, or a version step plus a similar description. Low: similar description only.
CVEs in this family
Table view of the tree| CVE | Published | Title | Linked from | Priority |
|---|---|---|---|---|
| CVE-2020-36049 | 7 Jan 2021 | socket.io-parser before 3.4.1 allows attackers to cause a denial of service (memory consumption) via a large packet… · fixed in 3.4.1 | First in chain | 17.1 |
| CVE-2022-2421 | 25 Oct 2022 | Socket.io - Improper type validation in attachment parsing · fixed in 4.2.1 | CVE-2020-36049 · related · High | 22.1 |
| CVE-2023-32695 | 27 May 2023 | Insufficient validation when decoding a Socket.IO packet · fixed in 4.2.3 | CVE-2022-2421 · related · High | 18.0 |