Tomofun Furbo 360/Furbo Mini UART Interface information disclosure

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
3.1$0-$5k0.35

Summaryinfo

A vulnerability marked as problematic has been reported in Tomofun Furbo 360 and Furbo Mini. This vulnerability affects unknown code of the component UART Interface. This manipulation causes information disclosure. This vulnerability is registered as CVE-2025-11634. It is feasible to perform the attack on the physical device. Furthermore, an exploit is available. The firmware versions determined to be affected are Furbo 360 up to FB0035_FW_036 and Furbo Mini up to MC0020_FW_074. The vendor was contacted early about this disclosure but did not respond in any way.

Detailsinfo

A vulnerability has been found in Tomofun Furbo 360 and Furbo Mini (Firmware Software) (the affected version is unknown) and classified as problematic. Affected by this vulnerability is an unknown code of the component UART Interface. The manipulation with an unknown input leads to a information disclosure vulnerability. The CWE definition for the vulnerability is CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. As an impact it is known to affect confidentiality.

The bug was discovered 05/15/2025. The weakness was published by Calvin Star, Julian B (skelet4r and dead1nfluence) with Software Secured. An attacker who is connected to the UART interface of the Furbo Mini can observe sensitive information being transmitted across the interface without requiring to authenticate with the device. Sensitive details include but aren't limited to: Firmware Decryption Key, DeviceToken, DeviceID, AccountID, P2P UUID and P2P Auth Details. These sensitive details can be used to perform various attacks against the victim device and account. This vulnerability is known as CVE-2025-11634. The exploitation appears to be easy. An attack has to be approached locally. The exploitation doesn't need any form of authentication. Technical details are unknown but a public exploit is available. MITRE ATT&CK project uses the attack technique T1592 for this issue.

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. The firmware versions determined to be affected are Furbo 360 up to FB0035_FW_036 and Furbo Mini up to MC0020_FW_074. Since UART is enabled by default on the Furbo Mini all an attacker would need in order to exploit this vulnerability would be some form of adapter that lets you read information being transmitted over the UART protocol. Once you connect that adapter to the Furbo Mini and then your Host device you can simply read the data that is being transmitted using screen or any other tool. Replication Steps: 1. Disassemble the Furbo Mini device. 2. Connect to the 4-pin UART port. 3. On your host device run: sudo screen /dev/ttyUSB0 115200 4. Start the Furbo Mini device 5. Observe as sensitive device details are all printed over UART.

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-33897). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Vendor

Name

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒

CVSSv3info

VulDB Meta Base Score: 3.1
VulDB Meta Temp Score: 3.1

VulDB Base Score: 2.4
VulDB Temp Score: 2.2
VulDB Vector: 🔒
VulDB Reliability: 🔍

NVD Base Score: 4.6
NVD Vector: 🔒

CNA Base Score: 2.4
CNA Vector: 🔒

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Information disclosure
CWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒

Physical: Yes
Local: Yes
Remote: No

Availability: 🔒
Access: Public
Status: Proof-of-Concept

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔒

Timelineinfo

05/15/2025 Vulnerability found
06/21/2025 +37 days Vendor informed
07/03/2025 +11 days Vendor acknowledged
10/11/2025 +99 days Advisory disclosed
10/11/2025 +0 days VulDB entry created
10/31/2025 +20 days VulDB entry last update

Sourcesinfo

Researcher: Calvin Star, Julian B (skelet4r, dead1nfluence)
Organization: Software Secured
Status: Not defined

CVE: CVE-2025-11634 (🔒)
GCVE (CVE): GCVE-0-2025-11634
GCVE (VulDB): GCVE-100-328045
EUVD: 🔒
scip Labs: https://www.scip.ch/en/?labs.20161013

Entryinfo

Created: 10/11/2025 20:38
Updated: 10/31/2025 04:51
Changes: 10/11/2025 20:38 (51), 10/12/2025 15:29 (29), 10/12/2025 16:23 (1), 10/13/2025 22:35 (7), 10/13/2025 22:36 (10), 10/13/2025 22:38 (7), 10/31/2025 04:51 (13)
Complete: 🔍
Submitter: jTag Labs
Committer: jTag Labs
Cache ID: 216::103

Submitinfo

Accepted

  • Submit #661353: Tomofun Furbo 360, Furbo Mini Furbo 360 (≤ FB0035_FW_036), Furbo Mini (≤ MC0020_FW_074) Insertion of Sensitive Information into Log File (by jTag Labs)

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Interested in the pricing of exploits?

See the underground prices here!