Unauthenticated device takeover via Cloud ID
Published Dec 1, 2022 · Updated Apr 24, 2025
Improper access control in GL.iNet GoodCloud 1.0 and earlier allows remote attackers to read or change managed-device settings. GoodCloud accepts a device Cloud ID without enforcing that the requester is authorized to control the associated device. Knowledge of a target's Cloud ID is sufficient to take control of its GoodCloud-managed device; no service interruption is reported.
Summary
What happened
Improper access control in GL.iNet GoodCloud 1.0 and earlier allows remote attackers to read or change managed-device settings. GoodCloud accepts a device Cloud ID without enforcing that the requester is authorized to control the associated device. Knowledge of a target's Cloud ID is sufficient to take control of its GoodCloud-managed device; no service interruption is reported.
The record
- CVE
- CVE-2022-44211
- Published
- Dec 1, 2022
- Updated
- Apr 24, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-284, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 1, 2022CVE publishedPublication date reported by the CVE source.
- Apr 24, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo