Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-11650: Use of Weak Hash in Tomofun Furbo 360

0
Low
VulnerabilityCVE-2025-11650cvecve-2025-11650
Published: Sun Oct 12 2025 (10/12/2025, 23:02:06 UTC)
Source: CVE Database V5
Vendor/Project: Tomofun
Product: Furbo 360

Description

A vulnerability was determined in Tomofun Furbo 360 and Furbo Mini. The impacted element is an unknown function of the file /etc/shadow of the component Password Handler. Executing manipulation can lead to use of weak hash. The physical device can be targeted for the attack. The attack requires a high level of complexity. The exploitability is regarded as difficult. The exploit has been publicly disclosed and may be utilized. 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.

AI-Powered Analysis

AILast updated: 10/12/2025, 23:13:51 UTC

Technical Analysis

CVE-2025-11650 identifies a security weakness in the Tomofun Furbo 360 and Furbo Mini pet camera devices, specifically in the password handling mechanism involving the /etc/shadow file. The vulnerability arises from the use of a weak cryptographic hash algorithm to protect password hashes, which could theoretically allow an attacker with physical access to the device to manipulate or extract password data. The attack complexity is high, requiring physical possession of the device and advanced technical skills, and no remote exploitation is possible. The affected firmware versions include Furbo 360 up to FB0035_FW_036 and Furbo Mini up to MC0020_FW_074. Despite public disclosure, the vendor has not responded or issued patches, leaving the vulnerability unmitigated. The CVSS 4.0 score is 1.0, indicating low severity due to limited confidentiality impact, no integrity or availability impact, and the necessity of physical access and high attack complexity. No known exploits have been observed in the wild. This vulnerability highlights the risk of weak cryptographic practices in IoT devices, especially those handling sensitive user data. Organizations using these devices should consider the risk primarily from a physical security perspective and monitor for any vendor updates.

Potential Impact

The primary impact of CVE-2025-11650 is the potential compromise of password hashes stored on the device due to weak hashing algorithms. For European organizations, the risk is limited because exploitation requires physical access to the device and advanced skills, reducing the likelihood of attack in typical enterprise environments. However, in scenarios where these devices are deployed in accessible locations (e.g., offices, public spaces), attackers could extract password hashes and attempt offline cracking, potentially leading to unauthorized access to device functions or user data. The vulnerability does not affect device availability or integrity directly, nor does it allow remote exploitation, limiting broader network impact. Still, organizations should consider the privacy implications, as these devices often capture video and audio data. The lack of vendor response and patches prolongs exposure. Overall, the impact on European organizations is low but non-negligible in environments with weak physical security controls or high-value targets using these devices.

Mitigation Recommendations

1. Restrict physical access to Tomofun Furbo 360 and Furbo Mini devices, especially in sensitive or public areas, to prevent attackers from obtaining the device for offline analysis. 2. Implement strict physical security policies and monitoring for IoT devices deployed within organizational premises. 3. Regularly audit and inventory IoT devices to identify vulnerable firmware versions and plan for replacement or isolation if patches are unavailable. 4. Monitor vendor communications for any firmware updates or security advisories addressing this vulnerability. 5. Consider network segmentation to isolate these devices from critical systems, limiting potential lateral movement if compromised. 6. Employ endpoint detection solutions capable of monitoring unusual device behavior or unauthorized access attempts. 7. Educate staff about the risks of physical device tampering and encourage reporting of lost or stolen devices. 8. If possible, disable or limit password-based authentication mechanisms on the device or replace with stronger authentication methods. 9. Evaluate alternative devices with stronger security postures for future deployments.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
VulDB
Date Reserved
2025-10-11T18:33:15.986Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 68ec3621b99bb870f150ee90

Added to database: 10/12/2025, 11:13:37 PM

Last enriched: 10/12/2025, 11:13:51 PM

Last updated: 10/13/2025, 12:32:10 AM

Views: 2

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats