Cyber Resilience

CVE-2024-52331

Crypto Weakness in Ecovacs Deebot 900 Firmware

Public PoCCrypto Weakness
Published
23 January 2025
Modified
02 October 2025
CVSS Score v4 7.7
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/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.0021 12th percentile
Risk Priority 55 floored blend · peak EPSS

Summary

CVE-2024-52331 is a high-severity Use of a Broken or Risky Cryptographic Algorithm (CWE-327) vulnerability in Ecovacs Deebot 900 Firmware. Its CVSS base score is 7.7 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Default Accounts (T1078.001); ranked at the 12th 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 CM-14 (Signed Components) and IA-5 (Authenticator Management) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2024-52331 is a vulnerability in ECOVACS robot lawnmowers and vacuums that stems from the use of a deterministic symmetric key for decrypting firmware updates. This design flaw enables an attacker to craft malicious firmware, encrypt it with the known key, and have it successfully decrypted and installed by the affected device. Published on 2025-01-23, the issue carries a CVSS 3.1 base score of 7.5 (AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H) and maps to CWEs-327 (Broken or Risky Cryptographic Algorithm), CWE-494 (Download of Code Without Integrity Check), and CWE-1391 (Use of Weak Cryptographic Primitive).

Exploitation requires network access with no privileges, but involves high attack complexity and user interaction, such as tricking a device owner into applying the attacker's firmware update. Successful exploitation grants high impacts on confidentiality, integrity, and availability, allowing full compromise of the robot's firmware and potentially enabling persistent control, data exfiltration, or physical manipulation of the device.

The vulnerability was detailed in security research presentations, including one from 37C3 2023 at https://dontvacuum.me/talks/37c3-2023/37c3-vacuuming-and-mowing.pdf and another from HITCON 2024 at https://dontvacuum.me/talks/HITCON2024/HITCON-CMT-2024_Ecovacs.html. No specific advisories or patches are referenced in available information.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

ECOVACS robot lawnmowers and vacuums use a deterministic symmetric key to decrypt firmware updates. An attacker can create and encrypt malicious firmware that will be successfully decrypted and installed by the robot.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1078.001 Default Accounts Stealth
Adversaries may obtain and abuse credentials of a default account as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion.
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.
T1110.001 Password Guessing Credential Access
Adversaries with no prior knowledge of legitimate credentials within the system or environment may guess passwords to attempt access to accounts.
T1195 Supply Chain Compromise Initial Access
Adversaries may manipulate products or product delivery mechanisms prior to receipt by a final consumer for the purpose of data or system compromise.
T1072 Software Deployment Tools Execution
Adversaries may gain access to and use centralized software suites installed within an enterprise to execute commands and move laterally through the network.
T1078 Valid Accounts Stealth
Adversaries may obtain and abuse credentials of existing accounts as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-11147Same product: Ecovacs Airbot Andy
CVE-2024-12078Same product: Ecovacs Airbot Andy
CVE-2024-52328Same product: Ecovacs Airbot Andy
CVE-2024-12079Same product: Ecovacs Airbot Andy
CVE-2025-30199Same product: Ecovacs Deebot T10
CVE-2025-30200Same product: Ecovacs Deebot T10
CVE-2025-30198Same product: Ecovacs Deebot T10
CVE-2024-52330Same product: Ecovacs Deebot T10
CVE-2024-52325Same product: Ecovacs Goat G1
CVE-2024-52327Same vendor: Ecovacs

Affected Assets

ecovacs
deebot 900 firmware
all versions
ecovacs
deebot n8 firmware
all versions
ecovacs
deebot t8 firmware
all versions
ecovacs
deebot n9 firmware
all versions
ecovacs
deebot t9 firmware
all versions
ecovacs
deebot n10 firmware
all versions
ecovacs
deebot t10 firmware
all versions
ecovacs
deebot x1 firmware
all versions
ecovacs
deebot t20 firmware
all versions
ecovacs
deebot x2 firmware
all versions
+4 more product configuration(s) — see NVD for full list

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)
  • 22 hardening rules · 10 OS baselines
Validate
Prove the fix (OWASP ASVS)
  • V6.2.2
  • V6.3.1
  • V6.3.2
  • V6.4.2

Mitigating Controls (NIST 800-53 r5) AI

Requires digital signature verification before component installation, directly stopping execution of code downloaded without integrity checks.

IA-5 directly requires management of authenticator strength, distribution, and replacement, stopping default or guessable credentials from being introduced or used.

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

Employs integrity verification tools that can identify missing or failed checks on downloaded software after the fact.

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.

ID.RA-09 full match
prevents

Directly requires assessing authenticity/integrity of software before acquisition and use, preventing unverified downloads.

PR.AA-01 mostly match
prevents

PR.AA-01's credential issuance and key-management processes directly block most weak/default credential usage, yet leave hard-coded or product-design instances of CWE-1391 only partially addressed.

PR.AA-03 mostly match
prevents

Password-strength policies in PR.AA-03 directly block weak authenticators, but the control leaves hard-coded/default credentials largely unaddressed.

PR.DS-02 mostly match
prevents

Requires cryptographic integrity protections (signatures/hashes) for data-in-transit, covering downloaded code.

PR.PS-01 mostly match
prevents

Hardened baselines and default-setting reviews directly block default/hard-coded creds (mostly), yet leave algorithmic guessing, reuse, and non-config sources of weak credentials untouched (partial).

PR.PS-05 mostly match
prevents

Prevents execution of unauthorized software, blocking the outcome of an unchecked download.

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.

degrades

Directly requires secure generation, distribution and storage of authentication credentials, eliminating default/hard-coded weak passwords.

degrades

Mandates secure authentication mechanisms that preclude use of weak or default credentials.

prevents

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

prevents

Secure-coding rules can prohibit hard-coded passwords, yet coverage depends on specific coding standards adopted.

finds

Security testing can discover weak credentials, but does not guarantee they are prevented by design.

prevents

Enforces secure baseline configurations that should remove default credentials, yet does not guarantee credential strength.

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 (5 rules)
  • 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
  • V-248575 OL 8 must prevent the installation of software, patches, service packs, device drivers, or operating system components of local packages without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. prevents CWE-494
  • V-248667 OL 8 must configure the use of the pam_faillock.so module in the /etc/pam.d/system-auth file. prevents CWE-1391
Oracle Linux 9 (1 rule)
  • V-271524 OL 9 must check the GPG signature of software packages originating from external software repositories before installation. prevents CWE-494
RHEL 7 (3 rules)
  • V-204447 The Red Hat Enterprise Linux operating system must prevent the installation of software, patches, service packs, device drivers, or operating system components from a repository without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. prevents CWE-494
  • V-204442 The Red Hat Enterprise Linux operating system must not have the rsh-server package installed. prevents CWE-1391
  • V-204448 The Red Hat Enterprise Linux operating system must prevent the installation of software, patches, service packs, device drivers, or operating system components of local packages without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. prevents CWE-494
RHEL 8 (2 rules)
  • V-230264 RHEL 8 must prevent the installation of software, patches, service packs, device drivers, or operating system components from a repository without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. prevents CWE-494
  • V-244533 RHEL 8 must configure the use of the pam_faillock.so module in the /etc/pam.d/system-auth file. prevents CWE-1391
RHEL 9 (1 rule)
  • V-257820 RHEL 9 must check the GPG signature of software packages originating from external software repositories before installation. prevents CWE-494
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
Windows 11 (1 rule)
  • V-253461 The system must be configured to prevent the storage of the LAN Manager hash of passwords. prevents CWE-327
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
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
Windows Server 2022 (1 rule)
  • V-254474 Windows Server 2022 must be configured to prevent the storage of the LAN Manager hash of passwords. prevents CWE-327

References