Access control bypass in beego
The route lookup process in beego prior to 1.12.9 and 2.x prior to 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).
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2022-31259US | critical9.8 | — | ||
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… | ||||
02
references
External citations — patches, advisories, analysis.
- https://github.com/advisories/GHSA-qx32-f6g6-fcfrADVISORY
- https://github.com/beego/beegoPACKAGE
- https://github.com/beego/beego/commit/228576173a236c81a2122923fcf8099ad294e009WEB
- https://github.com/beego/beego/commit/64cf44d725c8cc35d782327d333df9cbeb1bf2ddWEB
- https://github.com/beego/beego/issues/4946WEB
- https://github.com/beego/beego/pull/4954WEB
- https://github.com/beego/beego/pull/4958WEB
- https://github.com/beego/beego/tree/v2.0.2WEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan