CVE-2018-7360
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 information exposure vulnerability, which may allow an unauthenticated attacker to get the GPON SN information via appviahttp service.
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 confidenceThe ZTE ZXHN F670 router has an information disclosure vulnerability in the appviahttp service that allows unauthenticated remote attackers to obtain the GPON Serial Number (SN) through direct HTTP requests to the device.
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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 device modelAccess the router web management interface (typically at 192.168.1.1) and check the device info page, or look at the physical device label for the model numberAffected if The device is not a ZTE ZXHN F670 router - this CVE only applies to that specific model
-
Check the installed firmware versionIn the router web interface, navigate to Status or Device Info section and locate the firmware version field. Alternatively, access the diagnostic page or check via CLI if availableAffected if The firmware version is lower than 1.1.10p3t18 (e.g., V1.1.10P1T10, V1.1.05, etc.)
-
Test for the vulnerable endpointSend a direct HTTP GET request to the device's web server targeting the appviahttp service endpoint that exposes the GPON Serial Number. Use a tool like curl: curl http://<router-ip>/getterF quickeroute.cgi?images/Affected if The HTTP response returns the GPON Serial Number (SN) without requiring authentication - this indicates the vulnerable service is exposed and responding
-
Verify network accessibility of the management interfaceFrom an untrusted network (not the local LAN), attempt to access the router's HTTP management port (typically port 80). Use an external host or port scanner to test if port 80/443 is reachable from outside the local networkAffected if The router's web management interface is accessible from external/public IP addresses without firewall restrictions
The device is affected if it is a ZTE ZXHN F670 running firmware below version 1.1.10p3t18 AND the appviahttp service endpoint is accessible and returns the GPON Serial Number without authentication.
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
Update the router firmware to a version newer than V1.1.10P3T18, and implement network segmentation or firewall rules to restrict external access to the device management interface.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-7360 — 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-7360 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