Heap-based buffer overflow in ZTE ZXHN F670 can enable arbitrary code execution

Note: This data is for reference and cybersecurity research purposes only.CyStack advises users not to use this information for unlawful purposes.

Overview

Original source data

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.

Affected products and scope

  • ZTE ZXHN F670: All versions up to and including V1.1.10P3T18 are confirmed affected.
  • ZTE's bulletin identifies the product branch as ZXHN F670 V1.0 and lists V1.1.10P3T22 as the resolved version in its affected-products-and-fixes table.
  • The supplied CNA/NVD data confirms ZTE ZXHN F670 only. The bulletin's broader narrative mentions other CPE products, but this record does not extend confirmed affected status to those models.

Technical details

This is a heap-based buffer overflow, mapped by NVD to CWE-787, in ZTE ZXHN F670 firmware. A specially formed value could potentially write beyond an allocated heap buffer, but the record does not identify the exact input, parser, endpoint, memory operation, or vulnerable service, so a more specific attack path cannot be confirmed. The scoring evidence characterizes the issue as network reachable, requiring no privileges or user interaction; ZTE's assessment rates attack complexity high, while NVD rates it low. ZTE's assessment marks scope as changed and NVD's assessment marks it as unchanged, and neither source explains the relevant process boundary. The affected firmware boundary is stated specifically in affected_summary.

Exploitability

  • Reachability: Both assessments use a network attack vector.
  • Authentication and interaction: Both assessments state that no privileges and no user interaction are required.
  • Complexity: ZTE rates attack complexity high, while NVD rates it low. This disagreement is retained because the available technical evidence does not resolve it.
  • Exploitation status: The supplied record does not mark the issue as known exploited or associated with a public exploit, and the inspected vendor bulletin does not document either status. This is an evidence limitation, not evidence that exploitation has not occurred.

Technical impact

Successful exploitation could give an attacker arbitrary code execution on the device. That may affect confidentiality, integrity, or availability, including possible device manipulation or loss of service, but the record does not establish the exact execution context, privileges, persistence, or impact on connected networks. The disagreement between the vendor and NVD scope assessments means that the boundary of effects beyond the vulnerable component is not confirmed.

Business impact

An attacker who can reach a vulnerable device may be able to run code on it, with possible effects on router confidentiality, integrity, and availability. Depending on the execution context, this could enable unauthorized configuration changes, exposure of data handled by the device, or service disruption, but the record does not establish the resulting privileges or a confirmed compromise scenario. The network reachability and lack of required privileges in the scoring evidence make unpatched reachable devices the primary operational concern.

Remediation

  1. Upgrade ZTE ZXHN F670 to V1.1.10P3T22, which ZTE lists as the resolved version for the affected branch. This is exact branch-specific guidance; do not treat it as proof that every later or parallel branch has the same status.
  2. If the update cannot be applied, obtain deployment-specific mitigation guidance from ZTE. The available advisory does not document a product-specific workaround, so generic isolation or access-control measures should be treated as precautionary controls, not a confirmed fix.
  3. Verify the installed model and firmware after the change and retain the result in asset records. Devices whose branch cannot be matched to the affected or resolved entries should remain under review.

Detection

  1. Inventory each device's exact model, hardware or firmware branch, and installed firmware, then compare it with the affected and resolved entries in the advisory.
  2. Confirm that devices are not running a firmware state identified by the vendor as affected; do not infer safety from the hardware model alone.
  3. Review management and network telemetry for unexpected configuration changes, signs of code execution, or service disruption as a precaution. No CVE-specific log event, indicator, vulnerable endpoint, or forensic artifact is identified, and absence of such evidence does not prove safety.
  4. Escalate devices with an unverified branch or update status to ZTE or the internal product-security owner.
Sources (7)
Learn more

Run an in-depth assessment with complete web risk management

CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.