Skip to content

Commit 03a2c3c

Browse files
committed
docs(A5:2019): Add technical impact score
1 parent d5df4ba commit 03a2c3c

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

2019/en/0xa5-missing-function-resource-level-access-control.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ A5:2019 Missing Function/Resources Level Access Control
33

44
| Threat agents/Attack vectors | Security Weakness | Impacts |
55
| - | - | - |
6-
| API Specific : Exploitability **3** | Prevalence **2** : Detectability **1** | Technical **?** : Business Specific |
6+
| API Specific : Exploitability **3** | Prevalence **2** : Detectability **1** | Technical **2** : Business Specific |
77
| Exploitation requires the attacker to send legitimate API calls to the API endpoint they should not have access to. These endpoints might be exposed to anonymous users or regular, non-privileged users. It is easier to discover these flaws in APIs since APIs are more structured, and the way to access certain functions is more predictable (e.g. replacing the HTTP method from `GET` to `PUT`, or changing the “users” string in the URL to "admins") | Access control checks for a function or resource are usually managed via configuration, and sometimes at the code level. Implementing proper checks can be a confusing task since modern applications can contain many types of roles or groups and complex user hierarchy (e.g. sub-users, users with more than one role) | Such flaws allow attackers to access unauthorized functionality. Administrative functions are key targets for this type of attack |
88

99
## Is the API Vulnerable?

0 commit comments

Comments
 (0)