Unrestricted-Resource-KrishnaG-CEO

OWASP Top 10 API Security Risks – 2023: API4:2023 – Unrestricted Resource Consumption

Unrestricted resource consumption occurs when an API allows users or clients to request resources without proper limits or controls. Every API request consumes a certain amount of resources such as CPU cycles, memory, network bandwidth, storage, and other external services (e.g. email, SMS, or biometric validation). If these resources are not regulated, an attacker can exploit the API to consume disproportionate resources, leading to a range of undesirable consequences including:
Denial of Service (DoS): An attacker may cause the API to become unresponsive by overwhelming it with an excessive number of requests, or by requesting resources that are computationally expensive, leading to system crashes or slowdowns.
Inflated Operational Costs: APIs that involve third-party services, such as SMS or email delivery, may incur costs for each request. Without proper restrictions, malicious actors can generate high volumes of such requests, leading to unexpected cost overruns.
Data Loss or Degradation: APIs that allow unregulated access to large amounts of data or storage can be abused, resulting in slow system performance, data corruption, or loss.

Broken-Authorisation-KrishnaG-CEO

OWASP Top 10 API Security Risks – 2023: API1:2023 – Broken Object Level Authorisation

Broken Object Level Authorisation (BOLA) arises when APIs expose endpoints handling object identifiers without adequate access control measures. This vulnerability allows attackers to manipulate object IDs to gain unauthorised access to data.

Extraneous-Functionality-KrishnaG-CEO

OWASP Top 10 for Mobile Apps: M10 – Extraneous Functionality

Extraneous functionality can be defined as any feature or functionality that is present in a mobile application but is either unintentional or no longer needed. It may be left over from earlier stages of the development process, such as during testing or debugging, or added for convenience but overlooked as the application moves closer to production. Regardless of the reason for its existence, extraneous functionality represents a security risk.

Reverse-Engineering-KrishnaG-CEO

OWASP Top 10 for Mobile Apps: M9 – Reverse Engineering

Reverse engineering is the process of analysing a system or software to understand its components, functionality, and architecture. In the context of mobile apps, reverse engineering typically involves deconstructing an app’s compiled code to reveal its source code, data structures, and logic. The goal may be to identify vulnerabilities, extract sensitive data, or alter the app’s behaviour for malicious purposes.

Client-Code-Quality-KrishnaG-CEO

OWASP Top 10 for Mobile Apps: M7 – Client Code Quality

Client code quality refers to the soundness, reliability, and maintainability of the code executed on mobile devices. The “M7” designation in the OWASP Top 10 highlights vulnerabilities resulting from poorly written client-side code. These vulnerabilities can stem from inadequate input validation, insecure coding practices, or the use of deprecated libraries.