WiMAX routers based on the MediaTek SDK (libmtk) that use a custom httpd plugin are vulnerable to an authentication bypass allowing a remote
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.
- Published
- Jun 19, 2017
- Updated
- Jun 16, 2026
- EPSS
- 5.2% · 92th percentile
- CWE
- CWE-306
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
41
Plan
Add it to your regular patch cycle.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 2 / 30 · 5.2%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| greenpacket | ox350 firmware | cpe:2.3:o:greenpacket:ox350_firmware |
| greenpacket | ox350 | cpe:2.3:h:greenpacket:ox350 |
| huawei | bm2022 firmware | cpe:2.3:o:huawei:bm2022_firmware |
| huawei | bm2022 | cpe:2.3:h:huawei:bm2022 |
| huawei | hes-309m firmware | cpe:2.3:o:huawei:hes-309m_firmware |
| huawei | hes-309m | cpe:2.3:h:huawei:hes-309m |
| huawei | hes-319m firmware | cpe:2.3:o:huawei:hes-319m_firmware |
| huawei | hes-319m | cpe:2.3:h:huawei:hes-319m |
| huawei | hes-319m2w firmware | cpe:2.3:o:huawei:hes-319m2w_firmware |
| huawei | hes-319m2w | cpe:2.3:h:huawei:hes-319m2w |
| huawei | hes-339m firmware | cpe:2.3:o:huawei:hes-339m_firmware |
| huawei | hes-339m | cpe:2.3:h:huawei:hes-339m |
and 16 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- greenpacket ox350 firmwareall versions
- huawei bm2022 firmwareall versions
- huawei hes-309m firmwareall versions
- huawei hes-319m firmwareall versions
- huawei hes-319m2w firmwareall versions
- huawei hes-339m firmwareall versions
- mada soho wireless router firmwareall versions
- zte ox-330p firmwareall versions
- zyxel max218m firmwareall versions
- zyxel max218m1w firmwareall versions
- zyxel max218mw firmwareall versions
- zyxel max308m fimwareall versions
- zyxel max318m firmwareall versions
- zyxel max338m firmwareall versions
Versions reported by the vendor
Affected version ranges reported by the assigning authority (certcc). Independent of NVD's CPE analysis and usually ahead of it.
Green Packet OX350
- unknownaffected
Huawei Technologies BM2022
- 2.10.14affected
Huawei Technologies HES-309M
- unknownaffected
Huawei Technologies HES-319M
- unknownaffected
Huawei Technologies HES-319M2W
- unknownaffected
Huawei Technologies HES-339M
- unknownaffected
MADA Soho Wireless Router
- 2.10.13affected
ZTE OX-330P
- unknownaffected
ZyXEL MAX218M
- 2.00(UXG.0)D0affected
ZyXEL MAX218M1W
- 2.00(UXE.3)D0affected
ZyXEL MAX218MW
- 2.00(UXD.2)D0affected
ZyXEL MAX308M
- 2.00(UUA.3)D0affected
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-306 · Missing Authentication for Critical FunctionCVSS vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
A function added for development or support ships to production without authentication. It often relies on the assumption that it is “only reachable from the internal network.”
The bug in code
The whole CWE-306 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
// Added for the support teamapp.post("/maintenance/reset", resetDevice);Fixed
if (config.maintenanceEnabled) { app.post( "/maintenance/reset", requireSession, requireRole("admin"), resetDevice );}Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
- blog.sec-consult.com/2017/06/ghosts-from-past-authentication-bypass.html
- www.kb.cert.org/vuls/id/350135
Vendor advisories and official records. Exploit/PoC links are deliberately left out.