CVE-2026-105664: Guangzhou Juan IoT Technology EseeCloud Observable Response Discrepancy
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.
Affected Software
Event History
Frequently Asked Questions
What does an attacker need to exploit this issue?
The attacker needs a valid access token. No additional authentication or authorization is required to distinguish registered IDs from nonexistent ones.
Who is exposed to device enumeration?
EseeCloud deployments exposing the affected endpoint are at risk from any party that holds a valid access token. The endpoint can be used to identify registered devices across the 10-digit numeric ID space.
Why can this be exploited at scale?
The endpoint returns different error response codes for valid versus nonexistent IDs, creating an enumeration oracle. The absence of meaningful rate limiting allows repeated requests across a large range of candidate IDs.