CVE-2022-31836: GO-2022-0569 - Path traversal in github.com/beego/beego and beego/v2

CVE-2022-31836 · Severity: low · CVSS 3.1 · Published 2022-08-23

Path traversal 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-2022-31836 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2022-31836 being exploited in the wild.
How severe is CVE-2022-31836?
Low severity, with a CVSS score of 3.1, published 23 August 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.11; github.com/beego/beego/v2 (Go) SEMVER:introduced=2.0.0,fixed=2.0.4.
Is there a fix for CVE-2022-31836?
Yes. github.com/beego/beego (Go): upgrade to 1.12.11 or later; github.com/beego/beego/v2 (Go): upgrade to 2.0.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2022-31836?
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.11 or later
    go get github.com/beego/beego@v1.12.11
  • github.com/beego/beego/v2 (Go): upgrade to 2.0.4 or later
    go get github.com/beego/beego/v2@v2.0.4

Affected products

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

Identifiers

  • CVE-2022-31836
  • GHSA-95f9-94vc-665h
  • GO-2022-0569

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