# CVE-2017-8161: Security feature bypass in EVA-L09

> Attackers can bypass Factory Reset Protection on Huawei smartphones by manipulating the Swype application during reconfiguration.

- **Severity:** Medium 4.6 (`CVSS:3.0/AV:P/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Nov 2017
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-cf3m-48hf-6297

## What is CVE-2017-8161?

CVE-2017-8161 is a medium-severity vulnerability in Huawei Technologies Co., Ltd. EVA-L09, published on 22 Nov 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

EVA-L09 smartphones with software Earlier than EVA-L09C25B150CUSTC25D003 versions,Earlier than EVA-L09C440B140 versions,Earlier than EVA-L09C464B361 versions,Earlier than EVA-L09C675B320CUSTC675D004 versions have Factory Reset Protection (FRP) bypass security vulnerability. When re-configuring the mobile phone using the factory reset protection (FRP) function, an attacker can login the Swype and can perform some operations to update the Google account. As a result, the FRP function is bypassed.

Weakness: CWE-668 (Exposure of Resource to Wrong Sphere)

## Which versions are affected by CVE-2017-8161?

It affects 1 product.


Products: Huawei Eva-L09.

## How do I fix CVE-2017-8161?

No fix has been published for CVE-2017-8161 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-8161 being exploited?

There is no known exploitation of CVE-2017-8161 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-8161 and fix it if it is affected.

What it is: CVE-2017-8161 is a medium-severity vulnerability in Huawei Technologies Co., Ltd. EVA-L09, published on 22 Nov 2017. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-8161 in the wild and no public exploit code.

Affected product: Huawei Technologies Co., Ltd. EVA-L09. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-8161/ (Markdown: https://insights.sbomify.com/CVE-2017-8161/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-8161
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-8161
- OSV: https://osv.dev/vulnerability/CVE-2017-8161

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-8161/
Summaries are generated and may contain mistakes; the official description above is the record.