Chaingruntjs/gruntnpm:grunt
gruntjs/grunt: successive fixes (2020–2022)
3 CVEs over 3 generations, 3 Sep 2020 to 10 May 2022.
Family tree
Left to right by publication date.Oldest first. Select a CVE to open it.- CVE-2020-77293 Sep 2020 First in the chain
- CVE-2022-043612 Apr 2022 related to CVE-2020-7729
- CVE-2022-153710 May 2022 related to CVE-2022-0436related to CVE-2020-7729
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-7729 | 3 Sep 2020 | Arbitrary Code Execution · fixed in 1.3.0 | First in chain | 21.6 |
| CVE-2022-0436 | 12 Apr 2022 | Path Traversal in gruntjs/grunt · fixed in 1.5.2 | CVE-2020-7729 · related · High | 14.6 |
| CVE-2022-1537 | 10 May 2022 | file.copy operations in GruntJS are vulnerable to a TOCTOU race condition leading to arbitrary file write in… · fixed in 1.5.3 | CVE-2022-0436 · related · High | 10.0 |