CVE-2019-11063 json
SmartHome application has a broken access control vulnerability in its Web API Server
published 7y ago modified 4mo ago also EUVD-2019-2771
- cvss
- 10.0
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.9%
- EPSS 3.9% chance of exploitation in 30 days, percentile 90%
- public exploits
- 0
- none known
Summary
A broken access control vulnerability in SmartHome app (Android versions up to 3.0.42_190515, ios versions up to 2.0.22) allows an attacker in the same local area network to list user accounts and control IoT devices that connect with its gateway (HG100) via http://[target]/smarthome/devicecontrol without any authentication. CVSS 3.0 base score 10 (Confidentiality, Integrity and Availability impacts). CVSS vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H).
Patch / fix
- asus smarthome 2.0.22, 3.0.42_190515
Is CVE-2019-11063 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
3.95% chance of exploitation in the next 30 days, higher than 90% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- github.com https://github.com/tim124058/ASUS-SmartHome-Exploit/ referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 10.0 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H |
| NVD | 3.0 | 8.8 | CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 8.3 | AV:A/AC:L/Au:N/C:C/I:C/A:C |
Affected products
- ASUS SmartHome Android app
- ASUS SmartHome ios app
Classification
- Weakness
-
- CWE-306 Missing Authentication for Critical Functionality
References
-
github.com
/tim124058/ASUS-SmartHome-Exploit/
exploit, third-party-advisory
-
tvn.twcert.org.tw
/taiwanvn/TVN-201908014
third-party-advisory
-
surl.twcert.org.tw
/5LWQJ
third-party-advisory
Sources
- CVE List CVE-2019-11063
- NVD CVE-2019-11063
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.