Skip to content

Commit 50db5f7

Browse files
committed
fix(API1:2023): clarify the technical impact
1 parent 2a62a63 commit 50db5f7

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

2023/en/src/0xa1-broken-object-level-authorization.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ API1:2023 Broken Object Level Authorization
44
| Threat agents/Attack vectors | Security Weakness | Impacts |
55
| - | - | - |
66
| API Specific : Exploitability **3** | Prevalence **3** : Detectability **2** | Technical **3** : Business Specific |
7-
| Attackers can exploit API endpoints that are vulnerable to broken object-level authorization by manipulating the ID of an object that is sent within the request. Object IDs can be anything from sequential integers, UUIDs, or generic strings. Regardless the data type, they are easy to identify in the request target (path or query string parameters), requests headers, or even as part of the request payload. | This issue is extremely common in API-based applications because the server component usually does not fully track the client's state, and instead, relies more on parameters like object IDs, that are sent from the client to decide which objects to access. In most cases threat agents have full control over the request data, including object IDs. The server response is enough to understand whether the request was successful. | Unauthorized access can result in data disclosure to unauthorized parties, data loss, or data manipulation. Under certain circumstances, unauthorized access to objects can also lead to full account takeover. |
7+
| Attackers can exploit API endpoints that are vulnerable to broken object-level authorization by manipulating the ID of an object that is sent within the request. Object IDs can be anything from sequential integers, UUIDs, or generic strings. Regardless the data type, they are easy to identify in the request target (path or query string parameters), requests headers, or even as part of the request payload. | This issue is extremely common in API-based applications because the server component usually does not fully track the client's state, and instead, relies more on parameters like object IDs, that are sent from the client to decide which objects to access. In most cases threat agents have full control over the request data, including object IDs. The server response is enough to understand whether the request was successful. | Unauthorized access to other users' objects can result in data disclosure to unauthorized parties, data loss, or data manipulation. Under certain circumstances, unauthorized access to objects can also lead to full account takeover. |
88

99
## Is the API Vulnerable?
1010

0 commit comments

Comments
 (0)