# What is CVE-2017-17227? > CVE-2017-17227 is a high-severity flaw (CVSS 7.8) in Mate 10 from Huawei, published on 9 March 2018. It is not on the list of flaws known to be exploited today. The latest forecast puts its chance of use in the next 30 days at 1.0%. If you run an affected version, plan in the vendor’s fix. Canonical page: https://www.precursorintelligence.com/what-is/cve-2017-17227 ## At a glance - **Verdict:** Plan it in. No sign of exploitation and a low forecast. Patch it in your normal update cycle. - **Precursor Intelligence risk score:** 46 out of 100 (Medium); action: Plan remediation. Kept up to date as the evidence changes. - **Severity:** High (CVSS 7.8 out of 10) - **Known to be exploited:** No, not on the list of flaws known to be exploited today - **Chance of use in the next 30 days:** 1.0% (latest exploit-likelihood forecast) - **Published:** 9 March 2018 - **Record last updated:** 26 March 2018 - **Main product:** Mate 10 from Huawei - **Affected products:** 2 ## What is CVE-2017-17227? In plain terms An attacker has to be already on the device without logging in, but a person has to take an action first. If it works, the attacker can read data, change data and take it offline. ### The official description GPU driver in Huawei Mate 10 smart phones with the versions before ALP-L09 8.0.0.120(C212); The versions before ALP-L09 8.0.0.127(C900); The versions before ALP-L09 8.0.0.128(402/C02/C109/C346/C432/C652) has a out-of-bounds memory access vulnerability due to the input parameters validation. An attacker tricks a user into installing a malicious application on the smart phone, and the application can call the driver with special parameter and cause accessing out-of-bounds memory. Successful exploit may result in phone crash or arbitrary code execution. ### What kind of flaw is it? - CWE-125: Out-of-bounds Read - CWE-787: Out-of-bounds Write ### How an attack on it works - Where an attacker can be: Already on the device - How hard it is to pull off: Easy: no special conditions - Login needed first: No login needed - Does someone have to click: Yes, a person has to take an action - What an attacker gets: Can read data, change data and take it offline Severity vector: `CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H` ## Is CVE-2017-17227 being exploited? Not that we know of It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 1.0%. That can change at any time, which is why we keep watching. Exploit likelihood over the last 7 days: 1.0%, 1.0%, 1.0%, 1.0%, 1.0%, 1.0%, 1.0%. ### Timeline - 9 March 2018: Published - 26 March 2018: Record last updated ### How Precursor Intelligence ranks it CVE-2017-17227 scores **46 out of 100 (Medium)**, with the action "Plan remediation". Every published flaw gets a risk score from 0 to 100, kept up to date as the evidence changes. Four things go into the score, from the one that counts most to the ones that count less: - Evidence it is being exploited: biggest factor - How severe it is: strong factor - How widely exposed it is: smaller factor - Threat activity around it: smaller factor 85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score. When this flaw matches software you track, it lands in your list with its score and the reasons behind it. ## Who is affected by CVE-2017-17227? The published record lists 2 products. Versions are as published: "before alp-l09_8.0.0.120(c212)" means every version up to, but not including, alp-l09_8.0.0.120(c212). - [Mate 10](https://www.precursorintelligence.com/product/huawei/mate_10) by [Huawei](https://www.precursorintelligence.com/vendors/huawei) (Hardware): version not specified - [Mate 10 Firmware](https://www.precursorintelligence.com/product/huawei/mate_10_firmware) by [Huawei](https://www.precursorintelligence.com/vendors/huawei) (Operating system): before alp-l09_8.0.0.120(c212), before alp-l09_8.0.0.127(c900), before alp-l09_8.0.0.128(402), before alp-l09_8.0.0.128(c02), before alp-l09_8.0.0.128(c109), before alp-l09_8.0.0.128(c346), before alp-l09_8.0.0.128(c432), before alp-l09_8.0.0.128(c652) ## How do I fix CVE-2017-17227? 1. **Check whether you run it.** Compare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list. 2. **Apply the vendor’s fix.** Install the update named in the vendor’s advisory. We’ve put the advisory first in the list. 3. **If you can’t patch today.** Follow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in. 4. **Keep an eye on it.** Track the product and we tell you as soon as we spot this flaw on the list of exploited flaws, or a jump in its exploit likelihood. ### References - [huawei.com](http://www.huawei.com/en/psirt/security-advisories/huawei-sa-20180207-01-smartphone-en) (Vendor advisory) ## Questions ### What is CVE-2017-17227? CVE-2017-17227 is a high-severity flaw in Mate 10 from Huawei, published on 9 March 2018. An attacker has to be already on the device without logging in, but a person has to take an action first. If it works, the attacker can read data, change data and take it offline. ### How serious is CVE-2017-17227? It scores 7.8 out of 10 on the CVSS severity scale, which is high. Our risk score for CVE-2017-17227 is 46 out of 100, which is Medium. Its action is "Plan remediation". No sign of exploitation and a low forecast. Patch it in your normal update cycle. ### Is CVE-2017-17227 being exploited? It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 1.0%. That can change at any time, which is why we keep watching. ### Which versions does CVE-2017-17227 affect? For Mate 10 from Huawei: version not specified. The record lists 2 products in all, each with its versions, under "Who is affected" on this page. ### How do I fix CVE-2017-17227? Install the update the vendor names in its advisory, linked first under "How do I fix" on this page. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet. ## Does CVE-2017-17227 affect you? Precursor Intelligence keeps checking for you: - **Tell us what you run.** Pick your software from a list, or let us work it out from your website. - **We match it to every flaw.** Over 400,000 published flaws, checked against your list. - **Ranked by real-world risk.** Every flaw gets a 0 to 100 risk score, kept up to date, led by evidence criminals are using it. - **Told as soon as we know.** An alert by email, in the app or by webhook to your own tools. Start free (no card, nothing to install): https://www.precursorintelligence.com/register Book a demo: https://www.precursorintelligence.com/contact