The mobile application was found to contain stored credentials for the network it was developed on. If an attacker retrieved this, and found the physical location of the Wi-Fi network, they could gain unauthorized access to the Wi-Fi network of the vendor. Additionally, if an attacker were located in close physical proximity to the device when it was first set up, they may be able to force the device to auto-connect to an attacker-controlled access point by setting the SSID and password to the same as which was found in the firmware file.
The mobile application was found to store Wi-Fi network login credentials in plaintext (the network was used during product development) (CWE-312: Cleartext Storage of Sensitive Information). An attacker who obtains the application or firmware file can read the network name (SSID) and password. If the attacker determines the physical location of this network, they can attempt to gain unauthorized access. Additionally, an attacker in close physical proximity to the device during its initial configuration can set up their own access point with an identical SSID and password, forcing the device to automatically connect to the attacker-controlled network.
An attacker can gain unauthorized access to the manufacturer's Wi-Fi network or conduct a man-in-the-middle attack by substituting a malicious access point, which may lead to interception of the device's network traffic.
Hardcoded credentials must be removed from the mobile application code and firmware files. Authentication data should be stored in a secure, encrypted manner or should not be included in the application distribution at all. Patches available from the manufacturer should be applied according to the references.
Meatmeet mobile application (Meatmeet product); specific versions indicated in the manufacturer's references
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HMeatmeet
APPMeatmeet1.1.2.0
Related vulnerabilities
Ujawnienie informacji o nieopublikowanych urządzeniach w aplikacji Meatmeet Android
Meatmeet – transmisja danych w czystym tekście (HTTP), przechwycenie tokenów uwierzytelniania
Brak walidacji certyfikatu TLS w aplikacji mobilnej Meatmeet
The application uses an insecure hashing algorithm (MD5) to hash passwords. If an attacker obtained a copy of ...
The mobile application insecurely handles information stored within memory. By performing a memory dump on the...