CVE-2022-31259: GO-2022-0463 - Access control bypass due to broad route matching in github.com/beego/beego and beego/v2

Quick answers

Is CVE-2022-31259 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2022-31259 being exploited in the wild.

How severe is CVE-2022-31259?

Low severity, with a CVSS score of 3.1, published 1 July 2022.

Which products and versions are affected?

github.com/astaxie/beego (Go) SEMVER:introduced=0; github.com/beego/beego (Go) SEMVER:introduced=0,fixed=1.12.9; github.com/beego/beego/v2 (Go) SEMVER:introduced=0,fixed=2.0.3.

Is there a fix for CVE-2022-31259?

Yes. github.com/beego/beego (Go): upgrade to 1.12.9 or later; 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-2022-31259?

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 (Go): upgrade to 1.12.9 or later

  go get github.com/beego/beego@v1.12.9

• 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,fixed=1.12.9
• github.com/beego/beego/v2 (Go) SEMVER:introduced=0,fixed=2.0.3

Identifiers

• CVE-2022-31259
• GHSA-qx32-f6g6-fcfr
• GO-2022-0463