CVE-2022-31259Published May 21, 2022 · May 21Updated Oct 28
Access control bypass in beego
Critical9.8Fix available
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/beego/beego/v2 Go |
|
|
| github.com/beego/beego Go |
|
|
| github.com/astaxie/beego Go |
| Product | Affected | Fixed in |
|---|---|---|
| github.com/beego/beego/v2 Go |
|
|
| github.com/beego/beego Go |
|
|
| github.com/astaxie/beego Go |
all versions| No fix yet |
The route lookup process in beego before 1.12.9 and 2.x before 2.0.3 allows attackers to bypass access control. When a /p1/p2/:name route is configured, attackers can access it by appending .xml in various places (e.g., p1.xml instead of p1).
From the CVE record · mitre
Route lookup in affected beego packages can bypass access controls for a configured route such as /p1/p2/:name. An attacker can access the route by requesting a path with .xml appended to a segment, such as p1.xml instead of p1. The input does not specify whether authentication is required; no user interaction is described.
Check applications using Go github.com/beego/beego/v2 before 2.0.3, github.com/beego/beego before 1.12.9, or any version of github.com/astaxie/beego.