ChainRubyGems:geminabox
geminabox: successive fixes (2017)
3 CVEs over 3 generations, 25 Sep 2017 to 13 Nov 2017.
Family tree
Left to right by publication date.Oldest first. Select a CVE to open it.- CVE-2017-1450625 Sep 2017 First in the chain
- CVE-2017-1468325 Sep 2017 related to CVE-2017-14506
- CVE-2017-1679213 Nov 2017 related to CVE-2017-14683related to CVE-2017-14506
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-2017-14506 | 25 Sep 2017 | geminabox (aka Gem in a Box) before 0.13.6 has XSS, as demonstrated by uploading a gem file that has a crafted… · fixed in 0.13.6 | First in chain | 10.5 |
| CVE-2017-14683 | 25 Sep 2017 | geminabox (aka Gem in a Box) before 0.13.7 has CSRF, as demonstrated by an unintended gem upload · fixed in 0.13.7 | CVE-2017-14506 · related · High | 8.5 |
| CVE-2017-16792 | 13 Nov 2017 | Stored cross-site scripting (XSS) vulnerability in "geminabox" (Gem in a Box) before 0.13.10 allows attackers to… · fixed in 0.13.10 | CVE-2017-14683 · related · High | 13.0 |