Cyber Resilience

CVE-2025-11650

Crypto Weakness in Furbo Mini Firmware ≤ 074

Public PoCCrypto Weakness
Published
12 October 2025
Modified
29 April 2026
CVSS Score v4 0.3
Click a component to see what it means
Raw vectorCVSS:4.0/AV:P/AC:H/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0014 4th percentile
Risk Priority 9 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2025-11650 is a low-severity Use of a Broken or Risky Cryptographic Algorithm (CWE-327) vulnerability in Furbo Furbo Mini Firmware. Its CVSS base score is 0.3 (Low).

Operationally, exploitation aligns with the MITRE ATT&CK technique OS Credential Dumping (T1003); ranked at the 4th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SC-13 (Cryptographic Protection) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A04:2025 Cryptographic Failures

EU & UK References

Vulnerability Data

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…

more

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.

CWE(s)
CWE-327CWE-328

Related Threats

MITRE ATT&CK Enterprise Techniques

T1003 OS Credential Dumping Credential Access
Adversaries may attempt to dump credentials to obtain account login and credential material, normally in the form of a hash or a clear text password.
attack.mitre.org →
T1110 Brute Force Credential Access
Adversaries may use brute force techniques to gain access to accounts when passwords are unknown or when password hashes are obtained.
attack.mitre.org →
T1110.002 Password Cracking Credential Access
Adversaries may use password cracking to attempt to recover usable credentials, such as plaintext passwords, when credential material such as password hashes are obtained.
attack.mitre.org →
T1555 Credentials from Password Stores Credential Access
Adversaries may search for common password storage locations to obtain user credentials.
attack.mitre.org →
T1555.005 Password Managers Credential Access
Adversaries may acquire user credentials from third-party password managers.
attack.mitre.org →
T1557 Adversary-in-the-Middle Credential Access
Adversaries may attempt to position themselves between two or more networked devices using an adversary-in-the-middle (AiTM) technique to support follow-on behaviors such as [Network Sniffing](https://attack.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-11649Same product: Furbo Furbo 360 Dog Camera
CVE-2025-11643Same product: Furbo Furbo 360 Dog Camera
CVE-2025-11644Same product: Furbo Furbo 360 Dog Camera
CVE-2025-11639Same product: Furbo Furbo 360 Dog Camera
CVE-2025-11633Same product: Furbo Furbo 360 Dog Camera
CVE-2025-11640Same product: Furbo Furbo 360 Dog Camera
CVE-2025-11634Same product: Furbo Furbo 360 Dog Camera
CVE-2025-11647Same product: Furbo Furbo 360 Dog Camera
CVE-2025-11641Same product: Furbo Furbo 360 Dog Camera
CVE-2025-11638Same product: Furbo Furbo 360 Dog Camera

Affected Assets

furbo
furbo mini firmware
≤ 074
furbo
furbo 360 dog camera firmware
≤ 036

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)
  • 7 hardening rules · 4 OS baselines
Validate
Prove the fix (OWASP ASVS)
  • V11.2.3
  • V6.5.2

Mitigating Controls (NIST 800-53 r5) AI

SC-13 Cryptographic Protection good match

SC-13 requires selection and implementation of specific cryptography types, directly stopping use of broken algorithms.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 full match
prevents

Secure-SDLC requirements explicitly forbid weak cryptographic algorithms, fully preventing CWE-328 while covering only one aspect of development practice.

PR.DS-01 mostly match
prevents

Proper data-at-rest integrity protection requires strong cryptographic hashes, directly blocking weak-hash usage.

PR.DS-02 mostly match
prevents

Data-in-transit integrity likewise depends on strong hashes, so the control prevents the weakness while the weakness only partially satisfies the outcome.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.24 Use of cryptography mostly match
prevents

Mandating approved algorithms, cipher strength and usage standards directly stops the selection of broken or weak cryptographic primitives that attackers can exploit.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect weak-hash usage but does not prescribe algorithm choice.

A.5.31 Legal, statutory, regulatory and contractual requirements partial match
prevents

The explicit call-out of cryptography-related legal constraints (import/export, key escrow, digital-signature validity) reduces the likelihood that an organization will adopt broken or non-compliant cryptographic algorithms that violate those rules.

A.5.6 Contact with special interest groups partial match
prevents

Access to current specialist guidance and early vulnerability alerts enables timely replacement of broken or risky cryptographic algorithms with stronger alternatives.

A.8.26 Application security requirements partial match
prevents

Application security requirements can specify strong hashing, but the control is broader.

A.8.28 Secure coding partial match
prevents

Requires secure coding standards that forbid weak hash functions in source code.

Hardening callouts derived

Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).

Oracle Linux 8 (1 rule)
  • V-248524 OL 8 must implement NIST FIPS-validated cryptography for the following: To provision digital signatures, to generate cryptographic hashes, and to protect data requiring data-at-rest protections in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards. prevents CWE-327
Windows 10 (1 rule)
  • V-220937 The system must be configured to prevent the storage of the LAN Manager hash of passwords. prevents CWE-327, CWE-328
Windows Server 2016 (1 rule)
  • V-225053 Windows Server 2016 must be configured to prevent the storage of the LAN Manager hash of passwords. prevents CWE-327, CWE-328
Windows Server 2019 (1 rule)
  • V-205654 Windows Server 2019 must be configured to prevent the storage of the LAN Manager hash of passwords. prevents CWE-327, CWE-328

References