CVE-2022-31259
published 2022-05-21CVE-2022-31259: 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…
PriorityP266critical9.8CVSS 3.1
AVNACLPRNUINSUCHIHAH
EPSS
21.57%
97.3th percentile
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).
Affected
4 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| beego | beego | <= 1.12.4 | — |
| beego | beego | 2.0.0 – 2.0.2 | — |
| github.com | beego_beego | >= 0 < 1.12.9 | 1.12.9 |
| github.com | beego_beego_v2 | >= 0 < 2.0.3 | 2.0.3 |
CVSS provenance
nvdv3.19.8CRITICALCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvdv2.06.8MEDIUMAV:N/AC:M/Au:N/C:P/I:P/A:P
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
OSV
Access control bypass due to broad route matching in github.com/beego/beego and beego/v2
osv·2022-07-01
CVE-2022-31259 Access control bypass due to broad route matching in github.com/beego/beego and beego/v2
Access control bypass due to broad route matching in github.com/beego/beego and beego/v2
Routes in the beego HTTP router can match unintended patterns. This overly-broad matching may permit an attacker to bypass access controls.
For example, the pattern "/a/b/:name" can match the URL "/a.xml/b/". This may bypass access control applied to the prefix "/a/".
OSV
Access control bypass in beego
osv·2022-05-22
CVE-2022-31259 [CRITICAL] Access control bypass in beego
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).
GHSA
Access control bypass in beego
ghsa·2022-05-22
CVE-2022-31259 [CRITICAL] CWE-284 Access control bypass in beego
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).
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
https://beego.viphttps://github.com/advisories/GHSA-qx32-f6g6-fcfrhttps://github.com/beego/beego/issues/4946https://github.com/beego/beego/tree/v2.0.2https://beego.viphttps://github.com/advisories/GHSA-qx32-f6g6-fcfrhttps://github.com/beego/beego/issues/4946https://github.com/beego/beego/tree/v2.0.2
2022-05-21
Published