CVE-2021-30080: GO-2022-0572 - Access control bypass via incorrect route lookup in github.com/beego/beego and beego/v2

CVE-2021-30080 · Severity: info · Published 2022-08-22

Access control bypass via incorrect route lookup in github.com/beego/beego and beego/v2

Technologies: github.com/astaxie/beego (Go), github.com/beego/beego (Go), github.com/beego/beego/v2 (Go). Vendors: Go.

Quick answers

Is CVE-2021-30080 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2021-30080 being exploited in the wild.
How severe is CVE-2021-30080?
Informational severity, published 22 August 2022.
Which products and versions are affected?
github.com/astaxie/beego (Go) SEMVER:introduced=0; github.com/beego/beego (Go) SEMVER:introduced=0, SEMVER:introduced=0,last_affected=1.12.11; github.com/beego/beego/v2 (Go) SEMVER:introduced=2.0.0,fixed=2.0.3.
Is there a fix for CVE-2021-30080?
Yes. github.com/beego/beego/v2 (Go): upgrade to 2.0.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2021-30080?
Check whether you run github.com/astaxie/beego (Go), github.com/beego/beego (Go) or github.com/beego/beego/v2 (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • github.com/beego/beego/v2 (Go): upgrade to 2.0.3 or later
    go get github.com/beego/beego/v2@v2.0.3

Affected products

  • github.com/astaxie/beego (Go) SEMVER:introduced=0
  • github.com/beego/beego (Go) SEMVER:introduced=0, SEMVER:introduced=0,last_affected=1.12.11
  • github.com/beego/beego/v2 (Go) SEMVER:introduced=2.0.0,fixed=2.0.3

Identifiers

  • CVE-2021-30080
  • GHSA-28r6-jm5h-mrgg
  • GO-2022-0572

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.