# CVE-2017-3216: Auth bypass in BM2022

> Remote attackers can bypass authentication to gain administrator access on WiMAX routers using MediaTek SDK httpd plugins.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Jun 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-mf99-f92w-2rq5

## What is CVE-2017-3216?

CVE-2017-3216 is a critical authentication bypass vulnerability in Green Packet BM2022, published on 20 Jun 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

WiMAX routers based on the MediaTek SDK (libmtk) that use a custom httpd plugin are vulnerable to an authentication bypass allowing a remote, unauthenticated attacker to gain administrator access to the device by performing an administrator password change on the device via a crafted POST request.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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

It affects 14 products.


Products: Greenpacket Ox350 Firmware, Huawei Bm2022 Firmware, Huawei Hes-309m Firmware, Huawei Hes-319m2w Firmware, Huawei Hes-319m Firmware, Huawei Hes-339m Firmware, Mada Soho Wireless Router Firmware, Zte Ox-330p Firmware, Zyxel Max218m1w Firmware, Zyxel Max218m Firmware, Zyxel Max218mw Firmware, Zyxel Max308m Fimware, Zyxel Max318m Firmware, Zyxel Max338m Firmware.

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

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

## Is CVE-2017-3216 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-3216 is a critical authentication bypass vulnerability in Green Packet BM2022, published on 20 Jun 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-3216 in the wild and no public exploit code.

Affected product: Green Packet BM2022. 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-3216/ (Markdown: https://insights.sbomify.com/CVE-2017-3216/index.md)
```

## Sources

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

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