Tomofun Furbo Mobile App up to 7.57.0a on Android Authentication Token sensitive information
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 2.3 | $0-$5k | 0.00 |
Summary
A vulnerability categorized as problematic has been discovered in Tomofun Furbo Mobile App up to 7.57.0a on Android. This vulnerability affects unknown code of the component Authentication Token Handler. The manipulation results in sensitive information. This vulnerability is identified as CVE-2025-11645. An attack on the physical device is feasible. Additionally, an exploit exists. The vendor was contacted early about this disclosure but did not respond in any way.
Details
A vulnerability was found in Tomofun Furbo Mobile App up to 7.57.0a on Android. It has been classified as problematic. Affected is an unknown functionality of the component Authentication Token Handler. The manipulation with an unknown input leads to a sensitive information vulnerability. CWE is classifying the issue as CWE-922. The product stores sensitive information without properly limiting read or write access by unauthorized actors. This is going to have an impact on confidentiality.
The bug was discovered 05/15/2025. The weakness was released by Calvin Star, Julian B (skelet4r and dead1nfluence) with Software Secured. The advisory is shared for download at github.com. An attacker who obtains access to the device of a Furbo account owner may be able to retrieve the MFA AuthCode, Cognito Authentication token, as well as P2P authentication codes associated with the account from the device's memory. This information persists on the device after the mobile application has been closed. This vulnerability is traded as CVE-2025-11645. The exploitability is told to be easy. The attack needs to be approached locally. The exploitation doesn't require any form of authentication. Technical details are unknown but a public exploit is available. The MITRE ATT&CK project declares the attack technique as T1592.
A public exploit has been developed by Julian B (dead1nfluence) in JavaScript. The exploit is shared for download at github.com. It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 149 days. During that time the estimated underground price was around . The vendor was contacted early about this disclosure but did not respond in any way. Replication Steps: Preparation: 1. On a jail broken Android device, connect a web proxy such as Burp Suite or ZAP to monitor the traffic from the Furbo mobile application. 2. Open the application, authenticate. 3. Navigate around the application, connect to a device on your account. 4. Log out of the application. 5. Swipe up and close the application process. 6. In the web proxy history, locate a request to /v5/account/read/login, copy sensitive values from the response body such as the MFA Auth Code. 7. In the web proxy history, locate a request to /v5/device/p2p_connection/get and copy the values from the response body. Exploitation: 1. Ensure Frida has been installed on the mobile device running the Furbo App. 2. Download fridump3 from: https://github.com/rootbsd/fridump3 3. Run: fridump3 -v -u -s Furbo 4. In the output directory created, executed a grep command with partial strings from the response bodies collected in step 6 and 7 of preparation. For example: grep -ri ".eJwFwc26QkAAANB3aWtBfFMsWjD-" 5. Observe that these sensitive details were kept in memory, despite being signed out and the application having been closed.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-33908). VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 2.4VulDB Meta Temp Score: 2.3
VulDB Base Score: 2.4
VulDB Temp Score: 2.2
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 2.4
CNA Vector: 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Sensitive informationCWE: CWE-922 / CWE-200 / CWE-284
CAPEC: 🔒
ATT&CK: 🔒
Physical: Yes
Local: Yes
Remote: No
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Author: Julian B (dead1nfluence)
Programming Language: 🔒
Download: 🔒
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
05/15/2025 Vulnerability found06/21/2025 Vendor informed
07/03/2025 Vendor acknowledged
10/11/2025 Advisory disclosed
10/11/2025 VulDB entry created
10/18/2025 VulDB entry last update
Sources
Advisory: github.comResearcher: Calvin Star, Julian B (skelet4r, dead1nfluence)
Organization: Software Secured
Status: Not defined
CVE: CVE-2025-11645 (🔒)
GCVE (CVE): GCVE-0-2025-11645
GCVE (VulDB): GCVE-100-328056
EUVD: 🔒
scip Labs: https://www.scip.ch/en/?labs.20130704
Entry
Created: 10/11/2025 20:38Updated: 10/18/2025 23:29
Changes: 10/11/2025 20:38 (56), 10/12/2025 23:07 (1), 10/13/2025 00:19 (30), 10/18/2025 23:29 (16)
Complete: 🔍
Submitter: jTag Labs
Committer: jTag Labs
Cache ID: 216:F9F:103
Submit
Accepted
- Submit #661899: Tomofun Furbo Mobile Application ≤ 7.57.0a Insecure Storage of Sensitive Information (by jTag Labs)
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.