Due to a lack of certificate validation, all traffic from the mobile application can be intercepted. As a result, an adversary located "upstream" can decrypt the TLS traffic, inspect its contents, and modify the requests in transit. This may result in a total compromise of the user's account if the attacker intercepts a request with active authentication tokens or cracks the MD5 hash sent on login.
The lack of certificate pinning mechanism or other form of server certificate validation allows an attacker to perform a Man-in-the-Middle (MitM) attack. An attacker positioned between the application and the server can impersonate a trusted endpoint, decrypt encrypted TLS traffic, read its contents, and modify transmitted requests on the fly. It is particularly dangerous to intercept active authentication tokens or MD5 hash transmitted during the login process.
An attacker can gain full control over a user account by stealing session tokens or breaking the weak MD5 hash transmitted during login. It is also possible to modify data transmitted between the application and the server.
Patches available from the manufacturer should be applied according to the references. Additionally, it is recommended to implement certificate pinning in the mobile application and replace MD5 with a secure password hashing algorithm (e.g., bcrypt, Argon2).
Meatmeet mobile application (Meatmeet product) — versions specified in the manufacturer's references
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:NMeatmeet
APPMeatmeet1.1.2.0
Related vulnerabilities
Ujawnienie informacji o nieopublikowanych urządzeniach w aplikacji Meatmeet Android
Hardcoded credentials w aplikacji mobilnej Meatmeet
Meatmeet – transmisja danych w czystym tekście (HTTP), przechwycenie tokenów uwierzytelniania
The application uses an insecure hashing algorithm (MD5) to hash passwords. If an attacker obtained a copy of ...
Aplikacja mobilna w niebezpieczny sposób obsługuje informacje przechowywane w pamięci. Po wylogowaniu się użyt...