mobile app vulnerabilities

Extraneous-Functionality-KrishnaG-CEO

OWASP Top 10 for Mobile Apps: M10 – Extraneous Functionality

by

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

by

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.

Code-Tampering-KrishnaG-CEO

OWASP Top 10 for Mobile Apps: M8 – Code Tampering

by

Code tampering occurs when an attacker manipulates or alters the source code, binaries, or execution flow of a mobile application. This tampering can take various forms, including modifying the code to bypass security checks, reverse engineering to steal intellectual property, or injecting malicious code to steal sensitive data. Mobile apps, which often handle sensitive information like personal data, payment details, and corporate data, are prime targets for these attacks.

Client-Code-Quality-KrishnaG-CEO

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

by

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.

Insufficient-Cryptography-KrishnaG-CEO

OWASP Top 10 for Mobile Apps: M5 – Insufficient Cryptography

by

Cryptography, at its core, is the practice of securing communication and data through the use of algorithms and keys. For mobile apps, cryptography plays a crucial role in securing sensitive data, ensuring privacy, and maintaining the integrity of user interactions. However, *insufficient cryptography* occurs when an app fails to implement cryptographic algorithms or methods correctly, resulting in data being exposed or vulnerable to unauthorised access.

The issue of insufficient cryptography is particularly critical in mobile applications because of the increasing amount of sensitive information that these apps handle, such as financial data, personal identification information, passwords, and private conversations. Insufficient cryptography in this context means that sensitive data is not encrypted properly, or that weak or deprecated encryption methods are used, leaving the data open to attackers who can intercept, manipulate, or steal it.