Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| n/a | n/a | affected |
|
No data.
| Vendor | Product | Versions |
|---|---|---|
| Meatmeet | Meatmeet | — |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.149% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:meatmeet:meatmeet:1.1.2.0:*:*:*:pro:android:*:* |
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Meatmeet
Meatmeet meatmeet |
|
| Vendors & Products |
Meatmeet
Meatmeet meatmeet |
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-316 | |
| Metrics |
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | The mobile application insecurely handles information stored within memory. By performing a memory dump on the application after a user has logged out and terminated it, Wi-Fi credentials sent during the pairing process, JWTs used for authentication, and other sensitive details can be retrieved. As a result, an attacker with physical access to the device of a victim can retrieve this information and gain unauthorized access to their home Wi-Fi network and Meatmeet account. | |
| References |
|