Chainnpm:mysql2
mysql2: related fixes (2024)
3 CVEs over 3 generations, 10 Apr 2024 to 29 May 2024.
Family tree
Left to right by publication date.Oldest first. Select a CVE to open it.- CVE-2024-2150910 Apr 2024 First in the chain
- CVE-2024-2150811 Apr 2024 related to CVE-2024-21509
- CVE-2024-2151229 May 2024 related to CVE-2024-21509related to CVE-2024-21508
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-2024-21509 | 10 Apr 2024 | Versions of the package mysql2 before 3.9.4 are vulnerable to Prototype Poisoning due to insecure results object… · fixed in 3.9.4 | First in chain | 16.8 |
| CVE-2024-21508 | 11 Apr 2024 | Versions of the package mysql2 before 3.9.4 are vulnerable to Remote Code Execution (RCE) via the readCodeFor function… · fixed in 3.9.4 | CVE-2024-21509 · related · Medium | 23.9 |
| CVE-2024-21512 | 29 May 2024 | Versions of the package mysql2 before 3.9.8 are vulnerable to Prototype Pollution due to improper user input… · fixed in 3.9.8 | CVE-2024-21509 · related · Medium | 23.3 |