Skip to main content

Furbo 360 and Furbo Mini CVE-2025-11648

LOW
Server-Side Request Forgery (SSRF) (CWE-918)
2025-10-12 cna@vuldb.com
2.9
CVSS 4.0 · Vendor: vuldb
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Recon
    Enumerate BLE devices nearby
  2. Delivery
    Identify Furbo camera via BLE advertising
  3. Exploit
    Initiate BLE pairing
  4. Install
    Discover GATT service handling TF_FQDN.json
  5. C2
    Craft malicious JSON with attacker URL
  6. Execute
    Write modified payload to GATT characteristic
  7. Impact
    Device parses config and makes SSRF request
  8. Step 8
    Attacker intercepts or redirects response

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V4 - API and Web Service URL allowlisting, SSRF prevention
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Credential Access

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

CRITICAL CONDITION: Attacker must establish a Bluetooth Low Energy (BLE) connection to the target Furbo device. This requires the device to be in a pairable state (not all devices default to this) and the attacker to be in BLE radio range (typically 10-100 meters depending on environment). The attack targets the GATT Interface URL Handler component, specifically the TF_FQDN.json configuration file stored or processed by the device. BLE pairing may require user interaction (e.g., camera in setup mode or pairing enabled) depending on the device configuration, though the description does not explicitly mandate this. The CVSS vector AC:H indicates high attack complexity, reflecting that successful exploitation requires precise knowledge of the BLE protocol, correct GATT service UUID/characteristic discovery, and proper JSON payload structure. No authentication credentials are required once BLE pairing is established (PR:N). The vulnerability does NOT require network-layer compromise; it operates entirely over BLE, making it accessible to any attacker within physical/radio range of the device.

Impact

Risk is LOW in aggregate despite publicly available exploit code. CVSS v4.0 score of 2.9 with AC:H (high complexity) and limited scope (VC:L/VI:L/VA:L - low confidentiality, integrity, availability impact) accurately reflects the attack difficulty. EPSS score of 0.06% (18th percentile) confirms minimal real-world exploitation probability, suggesting this remains a niche technical vulnerability without widespread active exploitation. Attack vector is network (AV:N) and unauthenticated (PR:N), but the high attack complexity, requirement for BLE proximity to pair with the device, and manipulation of a configuration file that must be parsed correctly significantly increase the barrier to exploitation. Vendor non-response (unpatched for extended period) elevates concern from a supply-chain perspective, but the low CVSS impact scores and lack of KEV/active-in-the-wild signals indicate this is not an immediate critical threat to most deployments. Risk is primarily relevant to owners of these specific pet cameras who may be targeted by sophisticated attackers with physical or network proximity.

Exploit ScenarioDerived

An attacker within Bluetooth range (typically 30-100 meters for BLE) pairs with an unpatched Furbo 360 or Mini camera and sends a crafted BLE payload to modify the TF_FQDN.json file, injecting a malicious URL. When the device attempts to reach its backend services or check for firmware updates, it instead connects to an attacker-controlled server, leaking device identifiers, account tokens, or other sensitive data. Alternatively, the attacker could redirect requests to internal network services (e.g., 192.168.1.x API endpoints) to gather intelligence on the home network.

Monitor Track and reassess. Why: LOW severity (CVSS 0.1-3.9).
No patch listed yet 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Apr 29, 2026

Server-side request forgery in Tomofun Furbo 360 and Furbo Mini dog cameras allows remote attackers to manipulate the TF_FQDN.json configuration file via the GATT Interface URL Handler, enabling arbitrary internal network requests with low confidentiality and integrity impact. Affected firmware versions are Furbo 360 up to FB0035_FW_036 and Furbo Mini up to MC0020_FW_074. Publicly available exploit code exists, though the attack requires high complexity and is not actively exploited at scale per EPSS data (0.06%, percentile 18%).

RemediationAI

No vendor-released patch has been identified at time of analysis; Tomofun did not respond to early disclosure notification. Users should implement the following mitigations: (1) Restrict BLE connectivity to authorized devices only by disabling Bluetooth when not actively using the camera's mobile app - this eliminates the attack vector at the cost of losing remote Bluetooth features. (2) Network segmentation: isolate the camera to a separate VLAN or guest network with egress filtering to limit the impact of SSRF requests; this reduces data exfiltration risk but does not prevent the SSRF itself. (3) Monitor firmware update channels for any future security releases from Tomofun. (4) Users seeking immediate remediation should contact Tomofun support directly or consider replacing the device with an alternative that receives active security maintenance. Exploit code published on GitHub (https://github.com/dead1nfluence/Furbo-Advisories/blob/main/SSRF-via-BLE.md) demonstrates the BLE-based attack method.

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

This vulnerability exploits server-side request forgery (SSRF, CWE-918) in the GATT Interface URL Handler component of Furbo pet cameras. GATT (Generic Attribute Profile) is a Bluetooth Low Energy protocol used for device-to-device communication. The vulnerability allows manipulation of the TF_FQDN.json configuration file, which likely contains FQDN (Fully Qualified Domain Name) settings used by the device for API calls or firmware updates. By injecting malicious URLs into this configuration via BLE, an attacker can force the device to make HTTP/HTTPS requests to attacker-controlled or internal network destinations, potentially exfiltrating data or interacting with backend services. Affected products: Furbo 360 (cpe:2.3:o:furbo:furbo_360_dog_camera_firmware:*:*:*:*:*:*:*:*) and Furbo Mini (cpe:2.3:o:furbo:furbo_mini_firmware:*:*:*:*:*:*:*:*).

Know when Furbo Mini Firmware gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (vuldb) PRIMARY 2.9 LOW
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Primary rating from Vendor (vuldb) · only source for this CVE.

CVSS VectorVendor: vuldb

Attack Vector
Network
Attack Complexity
High
Attack Requirements
None
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
Low
Vulnerable system: Integrity
Low
Vulnerable system: Availability
Low
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

DescriptionCVE.org

A vulnerability has been found in Tomofun Furbo 360 and Furbo Mini. Impacted is an unknown function of the file TF_FQDN.json of the component GATT Interface URL Handler. Such manipulation leads to server-side request forgery. The attack may be performed from remote. Attacks of this nature are highly complex. The exploitability is considered 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.

Threat Intelligence Overview

EPSS Score
0.1%
Top 82% exploitable
Exploit
POC
Public exploit code exists
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity LOW
CISA KEV No
Public POC Yes
EPSS 0.1%
Patch available No
Active threat No
Deciding rule
LOW severity (CVSS 0.1-3.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
Poc
System Exposure· derived
Open
Automatable· derived
No
Human Impact· derived
Low

Priority Score

34
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +14
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Server-Side Request Forgery exploits applications that fetch remote resources based on user-supplied URLs.

Affected Products (CPE)CVE.org

cpe:2.3:o:furbo:furbo_mini_firmware:*:*:*:*:*:*:*:*
cpe:2.3:o:furbo:furbo_360_dog_camera_firmware:*:*:*:*:*:*:*:*
CVE-2025-11639 MEDIUM POC
4.8 Oct 12

Insecure local storage in Tomofun Furbo 360 and Furbo Mini firmware lets authenticated local users with low privileges a

CVE-2025-11649 MEDIUM
6.4 Oct 12

A hard-coded root password in the Tomofun Furbo 360 and Furbo Mini pet cameras allows local attackers with low privilege

CVE-2025-11643 MEDIUM
6.3 Oct 12

Hard-coded MQTT client certificate credentials in Furbo 360 (up to FB0035_FW_036) and Furbo Mini (up to MC0020_FW_074) f

CVE-2025-11633 MEDIUM
6.3 Oct 12

Tomofun Furbo 360 and Furbo Mini dog cameras running firmware up to FB0035_FW_036 and MC0020_FW_074 do not properly vali

CVE-2025-11646 LOW POC
2.1 Oct 12

Improper access controls in the GATT Service of Tomofun Furbo 360 and Furbo Mini dog cameras allow local network attacke

CVE-2025-11638 MEDIUM
5.3 Oct 12

Denial of service in Tomofun Furbo 360 and Furbo Mini cameras allows unauthenticated attackers on the adjacent network (

CVE-2025-11647 LOW POC
1.3 Oct 12

Information disclosure vulnerability in Tomofun Furbo 360 and Furbo Mini dog cameras allows local network attackers to e

CVE-2025-11644 LOW POC
0.3 Oct 12

Insecure storage of sensitive information in Tomofun Furbo 360 and Furbo Mini dog cameras via UART interface allows phys

CVE-2025-11650 LOW POC
0.3 Oct 12

Weak cryptographic hash implementation in Tomofun Furbo 360 and Furbo Mini firmware allows local attackers with low priv

CVE-2025-11642 MEDIUM
4.1 Oct 12

Denial of service in Tomofun Furbo 360 and Furbo Mini pet cameras occurs through the Registration Handler when a physica

CVE-2025-11634 LOW
2.4 Oct 12

Physical access to the UART debug interface on Tomofun Furbo 360 (firmware up to FB0035_FW_036) and Furbo Mini (up to MC

CVE-2025-11640 LOW
2.3 Oct 12

Cleartext transmission of sensitive information over Bluetooth Low Energy in Tomofun Furbo 360 and Furbo Mini firmware (

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy