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).
Metrics
Affected Vendors & Products
Advisories
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2022-5053 | The route lookup process in beego through 1.12.4 and 2.x through 2.0.2 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). |
Github GHSA |
GHSA-qx32-f6g6-fcfr | Access control bypass in beego |
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
No history.
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: mitre
Published:
Updated: 2024-08-03T07:11:39.910Z
Reserved: 2022-05-21T00:00:00
Link: CVE-2022-31259
No data.
Status : Modified
Published: 2022-05-21T19:15:52.990
Modified: 2024-11-21T07:04:14.560
Link: CVE-2022-31259
No data.
OpenCVE Enrichment
No data.
Weaknesses
EUVD
Github GHSA