CVE-2018-7363
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 authorization vulnerability. Since appviahttp service has no authorization delay, an attacker can be allowed to brute force account credentials.
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's appviahttp service lacks an authorization delay mechanism, enabling attackers to rapidly attempt credential combinations without time-based lockouts. This improper authorization allows brute-force attacks against user accounts.
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
- High
- Availability
- High
CVSS:3.0/AV:A/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the router modelAccess the router's web interface or check the device label to confirm the model is ZTE ZXHN F670Affected if The device is a ZTE ZXHN F670 router
-
Check the installed firmware versionLog into the router's web interface and navigate to the status or management page to view the firmware version, or use the command line if accessible (e.g., 'version' or 'cat /proc/version' via telnet/SSH if enabled)Affected if The firmware version is lower than 1.1.10p3t18 (e.g., 1.1.10p3t17 or earlier)
-
Verify if the appviahttp service is accessibleAttempt to access the router's web management interface over HTTP/HTTPS on the local network (typically ports 80 or 443) and confirm the appviahttp endpoint respondsAffected if The router's management interface and appviahttp service are reachable on the network
-
Check for brute-force protection mechanismsAttempt multiple failed login attempts to the router's web interface and observe if there is any time delay between attempts or account lockout after failed attemptsAffected if There is no delay between failed login attempts and no account lockout occurs after multiple failed attempts (the vulnerability means no protection exists)
You are affected if you have a ZTE ZXHN F670 router running firmware version lower than 1.1.10p3t18 and the appviahttp service is accessible on your network without any rate-limiting or account lockout protection in place.
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 vendor firmware update when available; until then, restrict access to the device's management interface via network segmentation or firewall rules to prevent external attackers from reaching the appviahttp service.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-7363 — 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-7363 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