Patchfirst
ChainGo:github.com/mattermost/mattermost-server

github.com/mattermost/mattermost-server: successive fixes (2016–2017)

18 CVEs over 4 generations, 19 Jun 2020 to 19 Jun 2020.

Family tree

Left to right by publication date.Oldest first. Select a CVE to open it.
  1. CVE-2016-1106819 Jun 2020 First in the chain
  2. CVE-2016-1106919 Jun 2020 No direct link to an earlier CVE
  3. CVE-2016-1107019 Jun 2020 No direct link to an earlier CVE
  4. CVE-2016-1108319 Jun 2020 No direct link to an earlier CVE
  5. CVE-2017-1887219 Jun 2020 No direct link to an earlier CVE
  6. CVE-2017-1887319 Jun 2020 next fix after CVE-2017-18876
  7. CVE-2017-1887419 Jun 2020 next fix after CVE-2017-18878
  8. CVE-2017-1887519 Jun 2020 next fix after CVE-2017-18874next fix after CVE-2017-18878
  9. CVE-2017-1887619 Jun 2020 next fix after CVE-2017-18874next fix after CVE-2017-18878
  10. CVE-2017-1887819 Jun 2020 No direct link to an earlier CVE
  11. CVE-2017-1890119 Jun 2020 No direct link to an earlier CVE
  12. CVE-2017-1890419 Jun 2020 related to CVE-2016-11083
  13. CVE-2017-1890519 Jun 2020 related to CVE-2017-18872
  14. CVE-2017-1891119 Jun 2020 next fix after CVE-2017-18918
  15. CVE-2017-1891519 Jun 2020 related to CVE-2017-18911related to CVE-2016-11068and 10 more
  16. CVE-2017-1891619 Jun 2020 related to CVE-2017-18911related to CVE-2016-11070
  17. CVE-2017-1891719 Jun 2020 related to CVE-2017-18915related to CVE-2016-11070and 1 more
  18. CVE-2017-1891819 Jun 2020 related to CVE-2016-11068related to CVE-2017-18915
19 Jun 2020 CVE-2017-18911 → CVE-2017-18915: related (high confidence)CVE-2017-18911 → CVE-2017-18916: related (high confidence)CVE-2017-18915 → CVE-2017-18917: related (high confidence)CVE-2016-11068 → CVE-2017-18915: related (medium confidence)CVE-2016-11068 → CVE-2017-18918: related (medium confidence)CVE-2016-11069 → CVE-2017-18915: related (medium confidence)CVE-2016-11070 → CVE-2017-18916: related (medium confidence)CVE-2016-11070 → CVE-2017-18917: related (medium confidence)CVE-2016-11083 → CVE-2017-18904: related (medium confidence)CVE-2016-11083 → CVE-2017-18915: related (medium confidence)CVE-2017-18872 → CVE-2017-18905: related (medium confidence)CVE-2017-18873 → CVE-2017-18915: related (medium confidence)CVE-2017-18874 → CVE-2017-18875: Next fix in the same package (medium confidence)CVE-2017-18874 → CVE-2017-18876: Next fix in the same package (medium confidence)CVE-2017-18874 → CVE-2017-18915: related (medium confidence)CVE-2017-18875 → CVE-2017-18915: related (medium confidence)CVE-2017-18876 → CVE-2017-18915: related (medium confidence)CVE-2017-18878 → CVE-2017-18915: related (medium confidence)CVE-2017-18901 → CVE-2017-18915: related (medium confidence)CVE-2017-18904 → CVE-2017-18915: related (medium confidence)CVE-2017-18905 → CVE-2017-18915: related (medium confidence)CVE-2017-18911 → CVE-2017-18917: related (medium confidence)CVE-2017-18915 → CVE-2017-18918: related (medium confidence)CVE-2017-18873 → CVE-2017-18876: Next fix in the same package (low confidence)CVE-2017-18874 → CVE-2017-18878: Next fix in the same package (low confidence)CVE-2017-18875 → CVE-2017-18878: Next fix in the same package (low confidence)CVE-2017-18876 → CVE-2017-18878: Next fix in the same package (low confidence)CVE-2017-18911 → CVE-2017-18918: Next fix in the same package (low confidence) CVE-2016-11068 19 Jun 2020 CVE-2016-11069 19 Jun 2020 CVE-2016-11070 19 Jun 2020 CVE-2016-11083 19 Jun 2020 CVE-2017-18872 19 Jun 2020 CVE-2017-18873 19 Jun 2020 CVE-2017-18874 19 Jun 2020 CVE-2017-18875 19 Jun 2020 CVE-2017-18876 19 Jun 2020 CVE-2017-18878 19 Jun 2020 CVE-2017-18901 19 Jun 2020 CVE-2017-18904 19 Jun 2020 CVE-2017-18905 19 Jun 2020 CVE-2017-18911 19 Jun 2020 CVE-2017-18915 19 Jun 2020 CVE-2017-18916 19 Jun 2020 CVE-2017-18917 19 Jun 2020 CVE-2017-18918 19 Jun 2020 19 Jun 2020 CVE-2017-18911 → CVE-2017-18915: related (high confidence)CVE-2017-18911 → CVE-2017-18916: related (high confidence)CVE-2017-18915 → CVE-2017-18917: related (high confidence)CVE-2016-11068 → CVE-2017-18915: related (medium confidence)CVE-2016-11068 → CVE-2017-18918: related (medium confidence)CVE-2016-11069 → CVE-2017-18915: related (medium confidence)CVE-2016-11070 → CVE-2017-18916: related (medium confidence)CVE-2016-11070 → CVE-2017-18917: related (medium confidence)CVE-2016-11083 → CVE-2017-18904: related (medium confidence)CVE-2016-11083 → CVE-2017-18915: related (medium confidence)CVE-2017-18872 → CVE-2017-18905: related (medium confidence)CVE-2017-18873 → CVE-2017-18915: related (medium confidence)CVE-2017-18874 → CVE-2017-18875: Next fix in the same package (medium confidence)CVE-2017-18874 → CVE-2017-18876: Next fix in the same package (medium confidence)CVE-2017-18874 → CVE-2017-18915: related (medium confidence)CVE-2017-18875 → CVE-2017-18915: related (medium confidence)CVE-2017-18876 → CVE-2017-18915: related (medium confidence)CVE-2017-18878 → CVE-2017-18915: related (medium confidence)CVE-2017-18901 → CVE-2017-18915: related (medium confidence)CVE-2017-18904 → CVE-2017-18915: related (medium confidence)CVE-2017-18905 → CVE-2017-18915: related (medium confidence)CVE-2017-18911 → CVE-2017-18917: related (medium confidence)CVE-2017-18915 → CVE-2017-18918: related (medium confidence)CVE-2017-18873 → CVE-2017-18876: Next fix in the same package (low confidence)CVE-2017-18874 → CVE-2017-18878: Next fix in the same package (low confidence)CVE-2017-18875 → CVE-2017-18878: Next fix in the same package (low confidence)CVE-2017-18876 → CVE-2017-18878: Next fix in the same package (low confidence)CVE-2017-18911 → CVE-2017-18918: Next fix in the same package (low confidence) CVE-2016-11068 19 Jun 2020 CVE-2016-11069 19 Jun 2020 CVE-2016-11070 19 Jun 2020 CVE-2016-11083 19 Jun 2020 CVE-2017-18872 19 Jun 2020 CVE-2017-18873 19 Jun 2020 CVE-2017-18874 19 Jun 2020 CVE-2017-18875 19 Jun 2020 CVE-2017-18876 19 Jun 2020 CVE-2017-18878 19 Jun 2020 CVE-2017-18901 19 Jun 2020 CVE-2017-18904 19 Jun 2020 CVE-2017-18905 19 Jun 2020 CVE-2017-18911 19 Jun 2020 CVE-2017-18915 19 Jun 2020 CVE-2017-18916 19 Jun 2020 CVE-2017-18917 19 Jun 2020 CVE-2017-18918 19 Jun 2020
Exploited in the wild (CISA KEV) Not in KEV Priority score (0 to 100) High confidence Medium Low

CVEs in this family

Table view of the tree
CVEPublishedTitleLinked fromPriority
CVE-2016-11068 19 Jun 2020 An issue was discovered in Mattermost Server before 3.2.0 · fixed in 3.2.0+incompatible First in chain 12.1
CVE-2016-11069 19 Jun 2020 An issue was discovered in Mattermost Server before 3.2.0 · fixed in 3.2.0+incompatible First in chain 11.9
CVE-2016-11070 19 Jun 2020 An issue was discovered in Mattermost Server before 3.1.0 · fixed in 3.1.0+incompatible First in chain 9.3
CVE-2016-11083 19 Jun 2020 An issue was discovered in Mattermost Server before 2.2.0 · fixed in 2.2.0+incompatible First in chain 10.6
CVE-2017-18872 19 Jun 2020 An issue was discovered in Mattermost Server before 4.4.3 and 4.3.3 · fixed in 4.4.3+incompatible First in chain 9.4
CVE-2017-18873 19 Jun 2020 An issue was discovered in Mattermost Server before 4.3.0, 4.2.1, and 4.1.2 · fixed in 4.3.0+incompatible CVE-2017-18876 · Next fix in the same package · Low 13.2
CVE-2017-18874 19 Jun 2020 An issue was discovered in Mattermost Server before 4.3.0, 4.2.1, and 4.1.2 when local storage for files is used · fixed in 4.3.0+incompatible CVE-2017-18878 · Next fix in the same package · Low 13.8
CVE-2017-18875 19 Jun 2020 An issue was discovered in Mattermost Server before 4.3.0, 4.2.1, and 4.1.2 when local storage for files is used · fixed in 4.3.0+incompatible CVE-2017-18874 · Next fix in the same package · Medium 10.8
CVE-2017-18876 19 Jun 2020 An issue was discovered in Mattermost Server before 4.3.0, 4.2.1, and 4.1.2 when local storage for files is used · fixed in 4.3.0+incompatible CVE-2017-18874 · Next fix in the same package · Medium 11.8
CVE-2017-18878 19 Jun 2020 An issue was discovered in Mattermost Server before 4.3.0, 4.2.1, and 4.1.2 · fixed in 4.3.0+incompatible First in chain 11.2
CVE-2017-18901 19 Jun 2020 An issue was discovered in Mattermost Server before 4.1.0, 4.0.4, and 3.10.3 · fixed in 4.0.4 First in chain 12.1
CVE-2017-18904 19 Jun 2020 An issue was discovered in Mattermost Server before 4.0.0, 3.10.2, and 3.9.2 · fixed in 3.10.2+incompatible CVE-2016-11083 · related · Medium 10.6
CVE-2017-18905 19 Jun 2020 An issue was discovered in Mattermost Server before 4.0.0, 3.10.2, and 3.9.2, when used as an OAuth 2.0 service… · fixed in 3.10.2+incompatible CVE-2017-18872 · related · Medium 11.1
CVE-2017-18911 19 Jun 2020 An issue was discovered in Mattermost Server before 3.8.2, 3.7.5, and 3.6.7 · fixed in 3.8.2+incompatible CVE-2017-18918 · Next fix in the same package · Low 10.4
CVE-2017-18915 19 Jun 2020 An issue was discovered in Mattermost Server before 3.8.2, 3.7.5, and 3.6.7 · fixed in 3.8.2+incompatible CVE-2017-18911 · related · High 13.6
CVE-2017-18916 19 Jun 2020 An issue was discovered in Mattermost Server before 3.8.2, 3.7.5, and 3.6.7 · fixed in 3.8.2+incompatible CVE-2017-18911 · related · High 11.1
CVE-2017-18917 19 Jun 2020 An issue was discovered in Mattermost Server before 3.8.2, 3.7.5, and 3.6.7 · fixed in 3.8.2+incompatible CVE-2017-18915 · related · High 10.8
CVE-2017-18918 19 Jun 2020 An issue was discovered in Mattermost Server before 3.7.3 and 3.6.5 · fixed in 3.7.3+incompatible CVE-2016-11068 · related · Medium 8.0
↑ ↓ chooseEnter openEsc close