CVE-2026-105664
Received Received - Intake

Observable Response Discrepancy in Device Enumeration Endpoint

Publication date: 2026-10-16

Last updated on: 2026-10-16

Assigner: ICS-CERT

Description
The endpoint exposes an observable response discrepancy when processing ID values. A request submitted with a nonexistent ID returns a distinct error response code from one submitted with a valid, registered ID, allowing an attacker holding a valid access token - but without further authentication or authorization - to distinguish valid ID values from the full 10-digit numeric search space. Combined with the absence of meaningful rate limiting on this endpoint, this discrepancy constitutes an enumeration oracle, enabling an attacker to discover registered devices at scale.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-16
Last Modified
2026-10-16
Generated
2026-10-16
AI Q&A
2026-10-16
EPSS Evaluated
N/A
NVD
CVE-2026-105664
EUVD
EUVD-2026-102880

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
Guangzhou Juan IoT Technology Co., Ltd. EseeCloud App 0
Guangzhou Juan IoT Technology Co., Ltd. EseeCloud Firmware 0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-204 The product provides different responses to incoming requests in a way that reveals internal state information to an unauthorized actor outside of the intended control sphere.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability involves an endpoint in the EseeCloud App and Firmware that processes ID values. When a request is made with a nonexistent ID, it returns a different error response than a valid ID. Attackers with a valid access token but no further authentication can exploit this to distinguish between valid and invalid IDs. Combined with the lack of rate limiting, this creates an enumeration oracle allowing attackers to discover registered devices at scale.

Detection Guidance

Monitor network traffic for repeated requests to the vulnerable endpoint with varying ID values. Check for distinct error responses between valid and invalid IDs. Use tools like Wireshark or tcpdump to capture and analyze HTTP responses for discrepancies in status codes or error messages.

Impact Analysis

Attackers could use this flaw to identify valid device IDs in your system, potentially leading to unauthorized access to device information or further attacks on registered devices. The lack of rate limiting means attackers can probe IDs rapidly, increasing the risk of discovery.

Compliance Impact

This vulnerability could lead to unauthorized access to device data, potentially violating privacy and security requirements under GDPR and HIPAA. Exposure of device IDs may enable attackers to gather sensitive information, compromising compliance with data protection regulations.

Mitigation Strategies

Immediately update EseeCloud App to version >4.9.6 and Firmware to version >4.9.86.0. Implement strict rate limiting on the vulnerable endpoint to prevent enumeration attempts. Disable or restrict access to the endpoint if updates are not feasible.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-105664. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart