Tomofun Furbo 360/Furbo Mini Debug Log S3 Bucket collect_logs.sh sensitive information
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.0 | $0-$5k | 0.09 |
Summary
A vulnerability, which was classified as problematic, was found in Tomofun Furbo 360 and Furbo Mini. This affects an unknown function of the file collect_logs.sh of the component Debug Log S3 Bucket Handler. The manipulation results in sensitive information. This vulnerability is known as CVE-2025-11639. Attacking locally is a requirement. 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.
Details
A vulnerability classified as problematic has been found in Tomofun Furbo 360 and Furbo Mini (Firmware Software) (affected version not known). Affected is some unknown functionality of the file collect_logs.sh of the component Debug Log S3 Bucket 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 published by Calvin Star, Julian B (skelet4r and dead1nfluence) with Software Secured. An attacker can retrieve the x-amz-grant-full-control ID from the collect_logs.sh file located on the Furbo device and use it to upload arbitrary data to the Furbo Device Debug Log S3 bucket. This may pollute the data source for Furbo, or result in a compromise of their systems or services if malware is uploaded and later executed. Additionally, as device IDs are issued sequentially, it is possible that an attacker could upload arbitrary files which would be associated with other Furbo user's devices This vulnerability is traded as CVE-2025-11639. The exploitability is told to be easy. Local access is required to approach this attack. Technical details and a private exploit are known. This vulnerability is assigned to T1592 by the MITRE ATT&CK project.
The exploit is shared for download at vuldb.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. The firmware versions determined to be affected are Furbo 360 up to FB0035_FW_036 and Furbo Mini up to MC0020_FW_074. The code used by the exploit is:
/usr/bin/curl -k --connect-timeout 60 -X PUT -T "$target" \
-H "Host: ${bucket}.s3.amazonaws.com" \
-H "Date: ${dateValue}" \
-H "Content-Type: ${contentType}" \
-H 'x-amz-grant-full-control: id="ad[REDACTED]a9a"' \
"${uri}/$fn" Replication Steps: 1. Connect to the Furbo device or unsquash the Furbo service file. 2. If on device, navigate to /tmp/furbo_app/bin/collect_logs.sh 3. Observe that the a-amz-grant-full-control header is stored in the file. This header can be used to upload files to the S3 bucket as if you were a Furbo device.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-33902). If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Vendor
Name
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: 4.0VulDB Meta Temp Score: 4.0
VulDB Base Score: 3.3
VulDB Temp Score: 3.2
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 5.5
NVD Vector: 🔒
CNA Base Score: 3.3
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: Partially
Local: Yes
Remote: No
Availability: 🔒
Access: Private
Status: Proof-of-Concept
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/29/2025 VulDB entry last update
Sources
Researcher: Calvin Star, Julian B (skelet4r, dead1nfluence)Organization: Software Secured
Status: Not defined
CVE: CVE-2025-11639 (🔒)
GCVE (CVE): GCVE-0-2025-11639
GCVE (VulDB): GCVE-100-328050
EUVD: 🔒
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 10/11/2025 20:38Updated: 10/29/2025 21:12
Changes: 10/11/2025 20:38 (52), 10/12/2025 20:06 (1), 10/12/2025 20:25 (29), 10/17/2025 07:50 (17), 10/17/2025 07:53 (5), 10/29/2025 21:12 (12)
Complete: 🔍
Submitter: jTag Labs
Committer: jTag Labs
Cache ID: 216:00E:103
Submit
Accepted
- Submit #661364: Tomofun Furbo 360, Furbo Mini Furbo 360 (≤ FB0035_FW_036), Furbo Mini (≤ MC0020_FW_074) Insecure Storage of Sensitive Information (by jTag Labs)
Duplicate
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.