Vulnerability Description
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).
CVSS Score
CRITICAL
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Beego | Beego | <= 1.12.4 |
References
- https://beego.vipProduct
- https://github.com/advisories/GHSA-qx32-f6g6-fcfr
- https://github.com/beego/beego/issues/4946ExploitIssue TrackingPatch
- https://github.com/beego/beego/tree/v2.0.2Release NotesThird Party Advisory
- https://beego.vipProduct
- https://github.com/advisories/GHSA-qx32-f6g6-fcfr
- https://github.com/beego/beego/issues/4946ExploitIssue TrackingPatch
- https://github.com/beego/beego/tree/v2.0.2Release NotesThird Party Advisory
FAQ
What is CVE-2022-31259?
CVE-2022-31259 is a vulnerability with a CVSS score of 9.8 (CRITICAL). 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 va...
How severe is CVE-2022-31259?
CVE-2022-31259 has been rated CRITICAL with a CVSS base score of 9.8/10. This is considered a critical vulnerability requiring immediate attention.
Is there a patch for CVE-2022-31259?
Check the references section above for vendor advisories and patch information. Affected products include: Beego Beego.