Executive Summary

This vulnerability occurs because the mobile application allows unencrypted (clear text) traffic to all domains and communicates with its API server over HTTP instead of HTTPS. This means an attacker positioned upstream in the network can intercept the data being sent, view its contents, and even modify the requests while they are in transit. This can lead to serious security issues such as account compromise if authentication tokens or hashed credentials are intercepted.

Useful 0 Not Useful 0

Impact Analysis

The vulnerability can lead to a total compromise of the user's account. An attacker intercepting the traffic can steal active authentication tokens or crack the MD5 hash sent during login, allowing them to impersonate the user, access sensitive information, and perform unauthorized actions within the application.

Useful 0 Not Useful 0

Mitigation Strategies

To mitigate this vulnerability, you should disable clear text traffic by configuring the mobile application to use HTTPS instead of HTTP for all communications with the API server. This prevents interception and modification of traffic by adversaries. Additionally, avoid sending sensitive information such as authentication tokens or passwords hashed with weak algorithms like MD5 over unencrypted channels.

Useful 0 Not Useful 0