ChainsinatraRubyGems:sinatra
sinatra: successive fixes (2018–2022)
4 CVEs over 3 generations, 31 May 2018 to 28 Nov 2022.
Family tree
Left to right by publication date.Oldest first. Select a CVE to open it.- CVE-2018-1162731 May 2018 First in the chain
- CVE-2022-299702 May 2022 related to CVE-2018-11627
- CVE-2022-363593 Aug 2022 No direct link to an earlier CVE
- CVE-2022-4544228 Nov 2022 related to CVE-2022-29970related to CVE-2022-36359
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-2018-11627 | 31 May 2018 | Sinatra before 2.0.2 has XSS via the 400 Bad Request page that occurs upon a params parser exception · fixed in 2.0.2 | First in chain | 16.4 |
| CVE-2022-29970 | 2 May 2022 | Sinatra before 2.2.0 does not validate that the expanded path matches public_dir when serving static files · fixed in 2.2.0 | CVE-2018-11627 · related · Medium | 16.4 |
| CVE-2022-36359 | 3 Aug 2022 | An issue was discovered in the HTTP FileResponse class in Django 3.2 before 3.2.15 and 4.0 before 4.0.7 · fixed in 4.0.7 | First in chain | 12.2 |
| CVE-2022-45442 | 28 Nov 2022 | Sinatra vulnerable to Reflected File Download attack · fixed in 3.0.4 | CVE-2022-29970 · related · High | 21.7 |