Tomofun Furbo 360/Furbo Mini HTTP Traffic collect_logs.sh upload_file_to_s3 certificate validation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.3 | $0-$5k | 0.00 |
Summary
A vulnerability labeled as critical has been found in Tomofun Furbo 360 and Furbo Mini. This affects the function upload_file_to_s3 of the file collect_logs.sh of the component HTTP Traffic Handler. The manipulation results in certificate validation.
This vulnerability is cataloged as CVE-2025-11633. The attack may be launched remotely. Furthermore, there is an exploit 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, which was classified as problematic, was found in Tomofun Furbo 360 and Furbo Mini (Firmware Software) (the affected version unknown). Affected is the function upload_file_to_s3 of the file collect_logs.sh of the component HTTP Traffic Handler. The manipulation with an unknown input leads to a certificate validation vulnerability. CWE is classifying the issue as CWE-295. The product does not validate, or incorrectly validates, a certificate. This is going to have an impact on integrity.
The bug was discovered 05/15/2025. The weakness was shared by Calvin Star, Julian B (skelet4r and dead1nfluence) with Software Secured. The vendor cooperated in the coordination of the public release. The Furbo 360 and Furbo mini both utilize a debug logging service called "Firehose" which executes a specific file called collect_logs.sh in order to collect and upload device data to their servers. This collect_logs.sh script has a vulnerable function called upload_file_to_s3() which utilizes the curl command with the -k argument in order to disable certificate verification on the request. This vulnerability means an attacker located upstream from the Furbo device can intercept the HTTPS traffic and decrypt it by impersonating the server and certificate. As a result, the attacker can decrypt the traffic and review the firehose logs which are transmitted to the server. These base64 encoded logs contain data about the user's account ID, device ID, configurations, and other information. This vulnerability is traded as CVE-2025-11633. The exploitability is told to be difficult. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. Technical details and a private exploit are known. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 10/31/2025). The MITRE ATT&CK project declares the attack technique as T1587.003. The reason for this vulnerability is this part of code:
upload_file_to_s3()
{
target="$1"
if [ ! -f "$target" ]; then
dlog "not found tarfile, skip upload s3"
return 1
fi
bucket=furbo2-device-debug-log
uri="https://furbo2-device-debug-log.s3.amazonaws.com"
datestr=`/bin/date +"%Y%m%d_%H%M%S"`
addr_pn="/sys/class/net/wlan0/address"
if [ -f $addr_pn ]; then
did="`/bin/cat $addr_pn | tr -d ':' | tr 'a-z' 'A-Z'`"
else
did="na"
fi
fn="${did}/${did}_${datestr}.tgz"
dateValue=`/bin/date -R`
contentType="application/x-compressed-tar"
/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="ad3b[REDACTED]a9a"' \
"${uri}/$fn"
ret=$?
if [ $ret -eq 0 ]; then
dlog "[s3] put file $fn successfully"
else
dlog "[s3] put file $fn failure"
fi
return $ret
}A private exploit has been developed by Aapo Oksman. 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. Although a dedicated exploit is not publicly available for this vulnerability several open source tools can be used in order to demonstrate this attack and confirm this vulnerability. Aapo Oksman has developed and published a tool called certmitm which can be used to test for certificate validation vulnerabilities of TLS connections made by a client device or an application. In order to use this tool to exploit this vulnerability you can use any sort of proxying tool to forward TLS traffic from the device to certmitm where the TLS connection can be tested for various configuration issues. In our research we used a combination for mitmrouter and certmitm in order to locate and exploit this vulnerability.
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-33892). Once again VulDB remains the best source for vulnerability data.
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.4VulDB Meta Temp Score: 4.3
VulDB Base Score: 3.7
VulDB Temp Score: 3.4
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 5.9
NVD Vector: 🔒
CNA Base Score: 3.7
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: Certificate validationCWE: CWE-295 / CWE-287
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Access: Private
Status: Proof-of-Concept
Author: Aapo Oksman
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/31/2025 VulDB entry last update
Sources
Researcher: Calvin Star, Julian B (skelet4r, dead1nfluence)Organization: Software Secured
Status: Not defined
Coordinated: 🔒
CVE: CVE-2025-11633 (🔒)
GCVE (CVE): GCVE-0-2025-11633
GCVE (VulDB): GCVE-100-328044
EUVD: 🔒
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 10/11/2025 20:38Updated: 10/31/2025 04:51
Changes: 10/11/2025 20:38 (51), 10/12/2025 14:23 (29), 10/12/2025 16:23 (1), 10/13/2025 22:33 (4), 10/13/2025 22:34 (17), 10/13/2025 22:37 (5), 10/31/2025 04:51 (13)
Complete: 🔍
Submitter: jTag Labs
Committer: jTag Labs
Cache ID: 216::103
Submit
Accepted
- Submit #661352: Tomofun Furbo 360, Furbo Mini Furbo 360 (≤ FB0035_FW_036), Furbo Mini (≤ MC0020_FW_074) Improper Certificate Validation (by jTag Labs)
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.