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-11642: Denial of Service in Tomofun Furbo 360

0
Medium
VulnerabilityCVE-2025-11642cvecve-2025-11642
Published: Sun Oct 12 2025 (10/12/2025, 19:02:05 UTC)
Source: CVE Database V5
Vendor/Project: Tomofun
Product: Furbo 360

Description

A vulnerability was identified in Tomofun Furbo 360 and Furbo Mini. Affected is an unknown function of the component Registration Handler. Such manipulation leads to denial of service. The attack can be executed directly on the physical device. The attack requires a high level of complexity. The exploitability is told to be difficult. 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, 19:27:18 UTC

Technical Analysis

CVE-2025-11642 identifies a denial of service vulnerability in Tomofun's Furbo 360 and Furbo Mini pet cameras, specifically within an unspecified function of the Registration Handler component. The vulnerability allows an attacker with physical access to the device to manipulate it in a way that causes a denial of service, rendering the device non-functional or unresponsive. The attack complexity is high, and exploitation is difficult, requiring no user interaction or authentication but physical proximity to the device. The affected firmware versions are Furbo 360 up to FB0035_FW_036 and Furbo Mini up to MC0020_FW_074. The vendor was notified early but has not issued any response or patches. The CVSS 4.1 score reflects medium severity, with attack vector being physical, high attack complexity, and no privileges or user interaction required. The vulnerability impacts device availability but does not affect confidentiality or integrity. No known exploits have been reported in the wild, limiting immediate risk. However, the lack of vendor response and patch availability means affected devices remain vulnerable. The Registration Handler likely manages device registration or pairing processes, and manipulation here could disrupt normal device operation. This vulnerability highlights risks in IoT devices where physical access can lead to service disruption, emphasizing the need for physical security and firmware update mechanisms.

Potential Impact

For European organizations, the primary impact of CVE-2025-11642 is operational disruption due to denial of service on Furbo 360 and Furbo Mini devices. While these devices are primarily consumer pet cameras, some organizations may use them for monitoring or security purposes in office or home environments. A successful attack could cause loss of video monitoring capability, potentially impacting security or surveillance functions. The physical access requirement limits remote exploitation risk but raises concerns in shared or public spaces where devices may be accessible. The medium severity and lack of confidentiality or integrity impact reduce the risk of data breaches but do not eliminate operational risks. The absence of vendor patches prolongs exposure and complicates remediation. European organizations with extensive IoT deployments or reliance on these devices should consider the risk of service interruption and potential cascading effects on security monitoring or pet care services. Additionally, reputational damage could occur if service outages affect customer-facing environments. Overall, the impact is moderate but non-negligible, especially in environments where device availability is critical.

Mitigation Recommendations

1. Enforce strict physical security controls to prevent unauthorized access to Furbo 360 and Furbo Mini devices, including placement in secure or monitored locations. 2. Monitor devices for signs of malfunction or unavailability that could indicate exploitation attempts. 3. Limit the number of personnel with physical access to these devices and maintain access logs where possible. 4. Segregate IoT devices on dedicated network segments to reduce potential lateral impact if devices become non-functional. 5. Regularly check for vendor updates or firmware patches addressing this vulnerability, and apply them promptly once available. 6. Consider disabling or restricting the Registration Handler functionality if configurable, or isolate the device from critical systems. 7. Implement incident response plans that include procedures for IoT device failures to minimize operational disruption. 8. Evaluate alternative devices with better security track records if Furbo devices are critical to operations. 9. Educate staff about the risks of physical tampering with IoT devices and encourage reporting of suspicious activity. 10. Engage with the vendor or community to advocate for vulnerability remediation and transparency.

Need more detailed analysis?Get Pro

Technical Details

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

Threat ID: 68ebfdab326426c3ce4b9041

Added to database: 10/12/2025, 7:12:43 PM

Last enriched: 10/12/2025, 7:27:18 PM

Last updated: 10/12/2025, 8:57:37 PM

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