ChainGo:github.com/beego/beego/v2
github.com/beego/beego/v2: successive fixes (2021–2022)
3 CVEs over 3 generations, 5 Apr 2022 to 5 Jul 2022.
Family tree
Left to right by publication date.Oldest first. Select a CVE to open it.- CVE-2021-300805 Apr 2022 First in the chain
- CVE-2022-3125921 May 2022 related to CVE-2021-30080
- CVE-2022-318365 Jul 2022 related to CVE-2022-31259
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-2021-30080 | 5 Apr 2022 | An issue was discovered in the route lookup process in beego before 1.12.11 that allows attackers to bypass access… · fixed in 2.0.3 | First in chain | 13.9 |
| CVE-2022-31259 | 21 May 2022 | The route lookup process in beego before 1.12.9 and 2.x before 2.0.3 allows attackers to bypass access control · fixed in 1.12.9 | CVE-2021-30080 · related · Medium | 19.5 |
| CVE-2022-31836 | 5 Jul 2022 | The leafInfo.match() function in Beego v2.0.3 and below uses path.join() to deal with wildcardvalues which can lead to… · fixed in 1.12.11 | CVE-2022-31259 · related · High | 15.3 |