dbcve.org
Zxhn F670 FirmwareOperating system · Zte

CVE-2018-7359

CRITICAL · 9.8 CVSS v3.0 Published 2018-11-16
Fix available
A fix is available. Upgrade to after 1.1.10p3t18 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
All versions up to V1.1.10P3T18 of ZTE ZXHN F670 product are impacted by heap-based buffer overflow vulnerability, which may allow an attacker to execute arbitrary code.

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 heap-based buffer overflow vulnerability exists in the ZTE ZXHN F670 router firmware in all versions up to V1.1.10P3T18. This memory corruption flaw allows remote attackers to overflow heap memory buffers, potentially enabling arbitrary code execution on the affected device.

MitigationApply the latest vendor firmware update beyond V1.1.10P3T18 when available. Until patched, restrict network access to the device's management interface and implement network segmentation to minimize exposure.

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
Zxhn F670 FirmwareOperating system
Affected:<= 1.1.10p3t18

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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. Identify the device model
    Access the router web management interface or check the device label to confirm the model is ZTE ZXHN F670
    Affected if Device is not a ZTE ZXHN F670 model
  2. Determine the firmware version
    Log into the router web interface and navigate to Status or System Info page to find the firmware version number
    Affected if Unable to retrieve firmware version information
  3. Compare firmware version against affected range
    Compare the installed firmware version to the affected range: any version up to and including V1.1.10P3T18 is vulnerable
    Affected if Firmware version is 1.1.10P3T18 or any earlier version (e.g., V1.1.10P2, V1.1.8, etc.)
  4. Verify the management interface is accessible
    Attempt to access the router web interface on the default IP (typically 192.168.1.1) from the local network
    Affected if Management interface responds to network requests

If the device is a ZTE ZXHN F670 router running firmware version 1.1.10P3T18 or any earlier version, the environment is affected by this CVE.

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
Upgrade available Upgrade to a release after 1.1.10p3t18
Interim mitigation

Apply the latest vendor firmware update beyond V1.1.10P3T18 when available. Until patched, restrict network access to the device's management interface and implement network segmentation to minimize exposure.

Recommended fix Moderate confidence

Any firmware version newer than V1.1.10P3T18 available from ZTE official support

  1. 1. Visit the official ZTE support portal at support.zte.com.cn and navigate to the firmware download section for the ZXHN F670 product.
  2. 2. Locate and download the latest available firmware version for the F670 router.
  3. 3. Access the router's web administration interface by entering the router's IP address (typically 192.168.1.1) in a web browser.
  4. 4. Log in with administrator credentials.
  5. 5. Navigate to the Administration or System settings section, then locate the Firmware Upgrade or Software Update option.
  6. 6. Upload the downloaded firmware file and initiate the upgrade process.
  7. 7. Wait for the upgrade to complete and the router to reboot automatically. Do not power off the router during this process.
  8. 8. After reboot, verify the new firmware version in the router's status page to confirm the upgrade was successful.
Caveat Review ZTE release notes for any configuration or feature changes in newer firmware versions before upgrading

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

Fix this in Zxhn F670 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-7359 — 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-2018-7359 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