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 15 floored blend · peak EPSS

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 /etc/passwd and /etc/shadow (T1003.008); 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 IA-5 (Authenticator Management) and SC-13 (Cryptographic Protection) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

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)

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

T1003.008 /etc/passwd and /etc/shadow Credential Access
Adversaries may attempt to dump the contents of <code>/etc/passwd</code> and <code>/etc/shadow</code> to enable offline password cracking.
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.
Why these techniques?

The vulnerability uses weak DES-based hashing for the root password in /etc/shadow, enabling dumping of credentials from /etc/shadow (T1003.008) and facilitating easy brute-force password cracking (T1110.002) with physical/filesystem access.

CVEs Like This One

CVE-2025-11646Same product: Furbo Furbo 360 Dog Camera
CVE-2025-11642Same product: Furbo Furbo 360 Dog Camera
CVE-2025-11640Same product: Furbo Furbo 360 Dog Camera
CVE-2025-11641Same product: Furbo Furbo 360 Dog Camera
CVE-2025-11639Same product: Furbo Furbo 360 Dog Camera
CVE-2025-11644Same product: Furbo Furbo 360 Dog Camera
CVE-2025-11633Same product: Furbo Furbo 360 Dog Camera
CVE-2025-11647Same product: Furbo Furbo 360 Dog Camera
CVE-2025-11648Same product: Furbo Furbo 360 Dog Camera
CVE-2025-11643Same 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)
  • IA-5 Authenticator Management
  • SC-13 Cryptographic Protection
  • SC-28 Protection of Information at Rest
Detect
Catch it (NIST detect / respond)

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

Mitigating Controls (NIST 800-53 r5) AI

prevent

Requires proper management and storage of authenticators, directly preventing use of weak hashes for passwords in /etc/shadow.

prevent

Mandates approved cryptographic algorithms and protections, eliminating the weak hashing (CWE-327/328) used by the password handler.

prevent

Requires cryptographic protection of information at rest, which would encompass proper hashing of credential data in the shadow file.

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.

prevents

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

detects

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

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.

prevents

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

prevents

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

prevents

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

References