dbcve.org
Mf286r FirmwareOperating system · Zte

CVE-2022-39067

MEDIUM · 6.5 CVSS v3.1 Published 2022-11-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
There is a buffer overflow vulnerability in ZTE MF286R. Due to lack of input validation on parameters of the wifi interface, an authenticated attacker could use the vulnerability to perform a denial of service attack.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A buffer overflow vulnerability exists in ZTE MF286R routers in the wifi interface due to insufficient input validation on wifi-related parameters. An authenticated attacker can send specially crafted requests with oversized input to trigger the overflow, causing the device to crash or become unresponsive.

MitigationImplement proper input length validation and bounds checking on all wifi interface parameters in the firmware. Until an official vendor patch is available, restrict administrative access to trusted users only and monitor for anomalous traffic.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Mf286r FirmwareOperating system
Affected:< mf286r_b07

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm router model is ZTE MF286R
    Log into the router administration interface or check the device label to verify the exact model number
    Affected if Device is not a ZTE MF286R router, then this specific CVE does not apply
  2. Identify the installed firmware version
    Access router admin panel (typically at 192.168.1.1 or 192.168.0.1), navigate to Status or System Info section to view the firmware version
    Affected if Firmware version is mf286r_b07 or any version lower than mf286r_b07 (the vulnerability affects versions before mf286r_b07)
  3. Verify Wi-Fi interface is enabled
    Check router wireless settings to confirm the Wi-Fi interface is active
    Affected if Wi-Fi interface is disabled, the specific attack surface may not be accessible but the vulnerable code may still be present in firmware
  4. Check if remote administration is accessible
    Examine router security settings to determine if the web management interface is exposed to the network (WAN) or only to local users (LAN)
    Affected if Remote administration is enabled and accessible from WAN, an unauthenticated network attacker could potentially reach the login page (though authentication is required for exploit)
  5. Monitor for device crashes or unresponsiveness
    Observe router behavior, particularly after network requests to Wi-Fi settings pages; check system logs for crashes or restart events
    Affected if Device exhibits unexpected crashes, reboots, or becomes unresponsive following Wi-Fi configuration changes or specific network requests

The environment is affected if the device is a ZTE MF286R router running firmware version mf286r_b07 or earlier, with Wi-Fi interface enabled and administrative access possible for an attacker.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper input length validation and bounds checking on all wifi interface parameters in the firmware. Until an official vendor patch is available, restrict administrative access to trusted users only and monitor for anomalous traffic.

Recommended fix Moderate confidence

mf286r_b07

  1. Obtain the mf286r_b07 firmware update from ZTE's official support portal at support.zte.com.cn
  2. Follow ZTE's standard firmware upgrade procedure for the MF286R device
  3. Verify the firmware has been successfully applied by checking the device's firmware version information
  4. Ensure the device is properly restarted after the upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Mf286r Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-39067 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-39067 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data