The mobile application insecurely handles information stored within memory.
The mobile application insecurely handles information stored within memory.
13 records
The mobile application insecurely handles information stored within memory.
The application uses an insecure hashing algorithm (MD5) to hash passwords.
Due to a lack of certificate validation, all traffic from the mobile application can be intercepted.
The ESP32 system on a chip (SoC) that powers the Meatmeet basestation device was found to lack Secure Boot.
An unauthenticated attacker within proximity of the Meatmeet device can issue several commands over Bluetooth Low Energy (BLE) to these devices which would result in a Denial of Service.
The mobile application is configured to allow clear text traffic to all domains and communicates with an API server over HTTP.
The mobile application was found to contain stored credentials for the network it was developed on.
The firmware on the basestation of the Meatmeet is not encrypted.
An unauthenticated attacker within proximity of the Meatmeet device can perform an unauthorized Over The Air (OTA) firmware upgrade using Bluetooth Low Energy (BLE), resulting in the firmware on the device being overwrit…
The Meatmeet Pro was found to be shipped with hardcoded Wi-Fi credentials in the firmware, for the test network it was developed on.
The ESP32 system on a chip (SoC) that powers the Meatmeet Pro was found to have JTAG enabled.
As UART download mode is still enabled on the ESP32 chip on which the firmware runs, an adversary can dump the flash from the device and retrieve sensitive information such as details about the current and previous Wi-Fi…
An issue was discovered in Meatmeet Android Mobile Application 1.1.2.0.