The NEW OWASP API top 10 — RC 2023

4 min readMar 25
Photo by Douglas Lopes on Unsplash

The Open Web Application Security Project (OWASP) is a global community of security professionals who aim to improve the security of web applications and APIs. One of their most popular projects is the OWASP API top 10, which is a list of the most common and critical security risks for APIs.

The OWASP API top 10 was first released in 2017, based on data from hundreds of real-world API security incidents and expert opinions. Since then, the API landscape has evolved significantly, with new technologies, standards, and threats emerging. Therefore, OWASP has decided to update the API top 10 to reflect the current state of API security.

The new OWASP API top 10 release candidate (RC) 2023 is now available for public review and feedback. The RC 2023 is based on a comprehensive data analysis of over 4000 API security incidents from various sources, such as bug bounty platforms, vulnerability databases, research papers, and industry reports. The RC 2023 also incorporates feedback from over 1000 API security experts and practitioners who participated in a survey conducted by OWASP.

The RC 2023 introduces some major changes to the previous version of the API top 10. Some of the risks have been renamed, restructured, or replaced to better reflect the current reality and severity of API security issues. The RC 2023 also provides more detailed descriptions, examples, attack scenarios, and mitigation strategies for each risk.

Here is a brief overview of the new OWASP API top 10 RC 2023:

1. Broken Object Level Authorization (BOLA): This risk occurs when an API exposes sensitive data or functionality that is not intended for the user’s access level. For example, an attacker may be able to access or modify another user’s data or resources by manipulating the object identifier in the API request.
2. Broken User Authentication (BUA): This risk occurs when an API fails to properly verify the identity and credentials of the user who is making the request. For example, an attacker may be able to bypass authentication mechanisms or exploit weak or stolen credentials to access or impersonate another user’s account.
3. Excessive Data Exposure (EDE): This risk occurs when an API returns more data than necessary for the intended functionality or purpose. For example, an attacker may be…


No b*llshit Hacking tutorials with extreme value in short bursts