CVE-2024-52330: ECOVACS lawnmowers and vacuums do not properly validate TLS certificates
Noroxi assessment
Priority: Monitor (action score 38/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.35% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
- Severity is disputed: the assigning authority (CNA) scores it 7.4, NVD 9.5.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
ECOVACS lawnmowers and vacuums do not properly validate TLS certificates. An unauthenticated attacker can read or modify TLS traffic, possibly modifying firmware updates.
- Published
- Jan 23, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.3% · 29th percentile
- CWE
- CWE-295
Report tools
Action score
38
Low priority for now.
- CVSS
- 38 / 40 · 9.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · cisa-cg
- 7.4
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Check your site's encryptionRun the SSL check
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| ecovacs | deebot x2 omni firmware | cpe:2.3:o:ecovacs:deebot_x2_omni_firmware |
| ecovacs | deebot x2 omni | cpe:2.3:h:ecovacs:deebot_x2_omni |
| ecovacs | deebot x2 combo firmware | cpe:2.3:o:ecovacs:deebot_x2_combo_firmware |
| ecovacs | deebot x2 combo | cpe:2.3:h:ecovacs:deebot_x2_combo |
| ecovacs | deebot x2s firmware | cpe:2.3:o:ecovacs:deebot_x2s_firmware |
| ecovacs | deebot x2s | cpe:2.3:h:ecovacs:deebot_x2s |
| ecovacs | deebot x5 pro firmware | cpe:2.3:o:ecovacs:deebot_x5_pro_firmware |
| ecovacs | deebot x5 pro | cpe:2.3:h:ecovacs:deebot_x5_pro |
| ecovacs | deebot x5 pro plus firmware | cpe:2.3:o:ecovacs:deebot_x5_pro_plus_firmware |
| ecovacs | deebot x5 pro plus | cpe:2.3:h:ecovacs:deebot_x5_pro_plus |
| ecovacs | deebot x5 pro ultra firmware | cpe:2.3:o:ecovacs:deebot_x5_pro_ultra_firmware |
| ecovacs | deebot x5 pro ultra | cpe:2.3:h:ecovacs:deebot_x5_pro_ultra |
and 28 more
Check your site's encryption
This vulnerability is about certificate validation or weak cryptography. The free SSL checker tests your certificate, enabled TLS versions and weak ciphers.
Run the SSL checkVersions reported by the vendor
Affected version ranges reported by the assigning authority (cisa-cg). Independent of NVD's CPE analysis and usually ahead of it.
ECOVACS DEEBOT T10
- 1.7.5not affected
- before 1.7.5affected
ECOVACS DEEBOT T10 OMNI
- 1.9.0not affected
- before 1.9.0affected
ECOVACS DEEBOT T10 PLUS
- 1.7.5not affected
- before 1.7.5affected
ECOVACS DEEBOT T10 TURBO
- 1.10.0not affected
- before 1.10.0affected
ECOVACS DEEBOT X1
- 1.7.3not affected
- before 1.7.3affected
ECOVACS DEEBOT X1 OMNI
- 2.4.41not affected
- before 2.4.41affected
ECOVACS DEEBOT X1 PLUS
- 1.7.3not affected
- before 1.7.3affected
ECOVACS DEEBOT X1 PRO OMNI
- 2.4.41not affected
- before 2.4.41affected
ECOVACS DEEBOT X1 TURBO
- 2.4.41not affected
- before 2.4.41affected
ECOVACS DEEBOT X1e OMNI
- 2.4.42not affected
- before 2.4.42affected
ECOVACS DEEBOT X1S PRO
- 2.5.31not affected
- before 2.5.31affected
ECOVACS DEEBOT X1S PRO PLUS
- 1.23.0not affected
- before 1.23.0affected
Affected versions · NVD (20)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- ecovacs deebot t10 firmwarebefore 1.7.5
- ecovacs deebot t10 omni firmwarebefore 1.9.0
- ecovacs deebot t10 plus firmwarebefore 1.7.5
- ecovacs deebot t10 turbo firmwarebefore 1.10.0
- ecovacs deebot x1 firmwarebefore 1.7.3
- ecovacs deebot x1 omni firmwarebefore 2.4.41
- ecovacs deebot x1 plus firmwarebefore 1.7.3
- ecovacs deebot x1 pro omni firmwarebefore 2.4.41
- ecovacs deebot x1 turbo firmwarebefore 2.4.41
- ecovacs deebot x1e omni firmwarebefore 2.4.42
- ecovacs deebot x1s pro firmwarebefore 2.5.31
- ecovacs deebot x1s pro plus firmwarebefore 1.23.0
- ecovacs deebot x2 combo firmwarebefore 1.81.10
- ecovacs deebot x2 omni firmwarebefore 1.76.6
- ecovacs deebot x2 pro firmwarebefore 1.76.6
- ecovacs deebot x2s firmwarebefore 1.49.0
- ecovacs deebot x5 pro firmwarebefore 1.70.0
- ecovacs deebot x5 pro plus firmwarebefore 1.38.0
- ecovacs deebot x5 pro ultra firmwarebefore 1.17.0
- ecovacs mate x firmwarebefore 1.44.18
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-295 · Improper Certificate ValidationCVSS vector
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:H/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
nvd-secondary
Root cause
A certificate validation error is silently swallowed instead of terminating the connection. Often, code added for a test environment makes its way into production.
The bug in code
The whole CWE-295 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
override fun checkServerTrusted(chain: Array<X509Certificate>, type: String) {
// Left empty for the test environment
}Fixed
val client = OkHttpClient.Builder()
.certificatePinner(
CertificatePinner.Builder()
.add("api.sirius.example", "sha256/…")
.build()
).build()Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (0)
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.