Chaintransloadit/uppynpm:@uppy/companion
transloadit/uppy: successive fixes (2020–2022)
4 CVEs over 4 generations, 20 Mar 2020 to 3 Mar 2022.
Family tree
Left to right by publication date.Oldest first. Select a CVE to open it.- CVE-2020-813520 Mar 2020 First in the chain
- CVE-2020-820520 Jul 2020 next fix after CVE-2020-8135
- CVE-2022-00864 Jan 2022 related to CVE-2020-8205
- CVE-2022-05283 Mar 2022 related to CVE-2020-8205next fix after CVE-2022-0086
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-8135 | 20 Mar 2020 | The uppy npm package < 1.9.3 is vulnerable to a Server-Side Request Forgery (SSRF) vulnerability, which allows an… · fixed in 1.9.3 | First in chain | 14.2 |
| CVE-2020-8205 | 20 Jul 2020 | The uppy npm package < 1.13.2 and < 2.0.0-alpha.5 is vulnerable to a Server-Side Request Forgery (SSRF) vulnerability… · fixed in 2.0.0-alpha.5 | CVE-2020-8135 · Next fix in the same package · Medium | 13.6 |
| CVE-2022-0086 | 4 Jan 2022 | Server-Side Request Forgery (SSRF) in transloadit/uppy · fixed in 3.1.5 | CVE-2020-8205 · related · Medium | 19.6 |
| CVE-2022-0528 | 3 Mar 2022 | Server-Side Request Forgery (SSRF) in transloadit/uppy · fixed in 3.3.1 | CVE-2020-8205 · related · Medium | 17.1 |