Menu

Star on GitHub · 3.2k

CVE-2017-17149

3.9 · LOW

Huawei HiWallet App with the versions before 8.0.4 has an arbitrary lock pattern change vulnerability.

Published Mar 9, 2018EPSS 0.22%

Overview

CVE-2017-17149 is a low-severity vulnerability. It was published on March 9, 2018 and has a CVSS 3.0 base score of 3.9 (LOW).

This vulnerability has a CVSS 3.0 base score of 3.9, rated LOW. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical description

Huawei HiWallet App with the versions before 8.0.4 has an arbitrary lock pattern change vulnerability. It needs to verify the user's Huawei ID during lock pattern change. An attacker with root privilege who gets a user's smart phone may bypass Huawei ID verification by special operation. Successful exploit of this vulnerability can allow an attacker to change the lock pattern of HiWallet.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2017-17149?

CVE-2017-17149 is a low-severity vulnerability. It was published on March 9, 2018 and has a CVSS 3.0 base score of 3.9 (LOW).

How severe is CVE-2017-17149?

This vulnerability has a CVSS 3.0 base score of 3.9, rated LOW. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2017-17149?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2017-17149?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2017-17149 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related LOW CVEs from 2017

View all