14:I[5228,["3385","static/chunks/3385-b76bb0d389ecb847.js","5753","static/chunks/5753-3df3dcd374d56bde.js","4462","static/chunks/4462-2f1547025558c923.js","1766","static/chunks/1766-e0a00c1dbb04d867.js","2122","static/chunks/2122-0aa89565809d0f14.js","8198","static/chunks/8198-02259efa89977c06.js","8058","static/chunks/8058-250b9e00e45a105b.js","2476","static/chunks/2476-39b31f73cd0731dd.js","4317","static/chunks/4317-05b07ec5dd2dfc17.js","8279","static/chunks/8279-51bfd849e487548c.js","9420","static/chunks/9420-af651d52266219df.js","1050","static/chunks/1050-c17118e9648df02f.js","9259","static/chunks/9259-b80e9833ae7b100c.js","7670","static/chunks/7670-77670847a8e0a1cb.js","1768","static/chunks/app/knowledgebases/%5BattackType%5D/%5Bid%5D/page-884b6d4b6fea536c.js"],"default"] 15:T4ed,The product defines policy namespaces and makes authorization decisions based on the assumption that a URL is canonical. This can allow a non-canonical URL to bypass the authorization. -------------

If an application defines policy namespaces and makes authorization decisions based on the URL, but it does not require or convert to a canonical URL before making the authorization decision, then it opens the application to attack. For example, if the application only wants to allow access to http://www.example.com/mypage, then the attacker might be able to bypass this restriction using equivalent URLs such as:

http://WWW.EXAMPLE.COM/mypage
http://www.example.com/%6Dypage (alternate encoding)
http://192.168.1.1/mypage (IP address)
http://www.example.com/mypage/ (trailing /)
http://www.example.com:80/mypage

Therefore it is important to specify access control policy that is based on the path information in some canonical form with all alternate encodings rejected (which can be accomplished by a default deny rule).

Use of Non-Canonical URL Paths for Authorization Decisions