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-11643: Hard-coded Credentials in Tomofun Furbo 360

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

Description

A security flaw has been discovered in Tomofun Furbo 360 and Furbo Mini. Affected by this vulnerability is an unknown functionality of the file /squashfs-root/furbo_img of the component MQTT Client Certificate. Performing manipulation results in hard-coded credentials. The attack may be initiated remotely. The attack's complexity is rated as high. The exploitation appears 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/19/2025, 19:59:00 UTC

Technical Analysis

CVE-2025-11643 identifies a security vulnerability in Tomofun Furbo 360 and Furbo Mini smart pet cameras, specifically within an unknown functionality related to the MQTT Client Certificate component located in the /squashfs-root/furbo_img file. The vulnerability arises from the presence of hard-coded credentials embedded in the firmware, which can be exploited remotely without requiring authentication, user interaction, or privileges. The affected firmware versions include Furbo 360 up to FB0035_FW_036 and Furbo Mini up to MC0020_FW_074. The attack complexity is rated as high, indicating that exploitation requires significant effort or specialized knowledge, and no known exploits have been observed in the wild to date. The vulnerability could allow an attacker to gain unauthorized access to the device's MQTT communication channel, potentially enabling interception or manipulation of data transmitted between the device and its cloud services. This could compromise confidentiality and integrity of the data, such as video streams or device commands. The vendor Tomofun was contacted early about the issue but has not provided any response or patch, leaving affected devices vulnerable. The CVSS 4.0 vector (AV:N/AC:H/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X) reflects a network attack vector with high complexity, no privileges or user interaction required, and limited impact on integrity. The lack of patch availability necessitates alternative mitigation strategies. This vulnerability highlights risks associated with embedded hard-coded credentials in IoT devices, which can undermine device security and user privacy.

Potential Impact

For European organizations, especially those in consumer electronics retail, smart home service providers, or enterprises deploying smart pet cameras in office environments, this vulnerability poses a risk of unauthorized access to device communications. The potential compromise of MQTT channels could lead to interception of video feeds or manipulation of device functions, impacting confidentiality and integrity. Although the attack complexity is high and exploitation is difficult, the absence of vendor response and patches prolongs exposure. Privacy regulations such as GDPR may also be implicated if personal data streams are intercepted. The impact is more pronounced in environments where these devices are integrated into broader IoT ecosystems, potentially serving as entry points for lateral movement. However, the limited scope and lack of known exploits reduce the immediate threat level. Organizations relying on these devices should consider the risk in their security posture and supply chain assessments.

Mitigation Recommendations

Given the absence of vendor patches, European organizations should first inventory all Tomofun Furbo 360 and Furbo Mini devices to identify affected firmware versions. Where possible, isolate these devices on segmented networks to limit exposure to untrusted networks and reduce attack surface. Employ network-level controls such as firewall rules to restrict MQTT traffic to trusted endpoints only. Monitor network traffic for unusual MQTT activity indicative of exploitation attempts. Consider disabling or replacing vulnerable devices if firmware updates are unavailable. Engage with Tomofun for status on patch development and advocate for timely remediation. Additionally, implement compensating controls like enhanced logging and anomaly detection on IoT device communications. For future procurement, prioritize devices with transparent security practices and timely patch management. Finally, raise user awareness about the risks of embedded credentials in IoT devices and encourage secure configuration practices.

Need more detailed analysis?Get Pro

Technical Details

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

Threat ID: 68ec04772ad1f36bd948e97a

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

Last enriched: 10/19/2025, 7:59:00 PM

Last updated: 12/4/2025, 2:09:26 AM

Views: 93

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