CVE-2018-7362
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 · uneditedAll versions up to V1.1.10P3T18 of ZTE ZXHN F670 product are impacted by improper access control vulnerability, which may allows an unauthorized user to perform unauthorized operations on the router.
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 · moderate confidenceThe ZTE ZXHN F670 router contains an improper access control vulnerability in all versions up to V1.1.10P3T18. This allows unauthorized users to bypass authentication mechanisms and perform administrative operations on the router without proper credentials.
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< 1.1.10p3t18CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the router firmware versionLog into the ZTE ZXHN F670 web management interface (typically at 192.168.1.1) and navigate to Status or System Information page to view the firmware version. Alternatively, access the router via CLI/telnet and check the version information.Affected if The displayed firmware version is earlier than V1.1.10P3T18, or the version cannot be determined.
-
Verify remote management statusIn the router web interface, locate the Remote Management or Remote Administration settings (usually under Advanced or Security settings). Check whether remote access via WAN is enabled.Affected if Remote management is enabled and the router is accessible from external networks.
-
Confirm router network exposureAttempt to access the router's web interface from an external network (outside your LAN) or use an online port scanner to check if ports used for router management (such as HTTP port 80, HTTPS port 443, or telnet) are exposed to the WAN.Affected if The router management interface is reachable from the internet or an untrusted network.
You are affected if your ZXHN F670 router runs firmware versions prior to V1.1.10P3T18 AND has remote management enabled or is exposed to untrusted networks.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor data1.1.10p3t18
Apply the vendor-supplied firmware patch when available. Until then, restrict network access to the router's management interface using firewall rules or VLAN segmentation, and disable remote management if not required.
- Consultation3.0 h
- Implementation3.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,360.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-7362 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-7362 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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