Email enumeration and account ID leakage vulnerabilities in ZTE SmartLife APP
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| ZTE | SmartLife | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Zte | Ztesw |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.333% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Zte
Zte ztesw |
|
| Vendors & Products |
Zte
Zte ztesw |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | SmartLife app dynamically generates brand‑new SmartLife application authentication parameters within its runtime process. With the obtained SmartLife application authentication parameters, attackers can directly invoke the backend interface /account/verify.serv to determine whether a target email address is registered for a SmartLife account. If the account exists, the real backend account ID can also be retrieved. | |
| Title | Email enumeration and account ID leakage vulnerabilities in ZTE SmartLife APP | |
| Weaknesses | CWE-269 | |
| References |
| |
| Metrics |
cvssV3_1
|