CVE-2019-3417
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 command injection vulnerability. Due to insufficient parameter validation check, an authorized user can exploit this vulnerability to take control of user router system.
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 confidenceCommand injection vulnerability in ZTE ZXHN F670 routers allows authenticated users to execute arbitrary operating system commands due to insufficient parameter validation. The vulnerability affects all firmware versions up to V1.1.10P3T18, enabling complete router compromise.
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.1/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.
-
Confirm router model is ZTE ZXHN F670Log into the router web management interface or check the device label. The model number should be listed as 'ZXHN F670' or 'ZTE ZXHN F670'.Affected if The device is not a ZTE ZXHN F670 router, then this CVE does not apply.
-
Check installed firmware versionIn the router web interface, navigate to the Status or Management section to view the firmware version. Compare the version number to 'V1.1.10P3T18'. Versions up to and including this version are affected.Affected if The firmware version is V1.1.10P3T18 or any earlier version (for example, V1.1.10P2T18, V1.1.8, etc.).
-
Verify web management interface is enabledCheck if the router's web-based management interface is accessible from the network. This is typically on HTTP/HTTPS port 80 or 443. Attempt to reach the login page.Affected if The web management interface is accessible and the device is on a network where attackers could potentially authenticate.
-
Confirm authentication is possibleDetermine if default credentials are still in use or if valid admin credentials can be obtained. The vulnerability requires an authenticated session to exploit.Affected if An attacker can obtain valid admin credentials to log into the router web interface.
A user is affected if they are running a ZTE ZXHN F670 router with firmware version V1.1.10P3T18 or earlier, with the web management interface accessible and authentication possible.
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 dataUpdate router firmware to a patched version beyond V1.1.10P3T18 provided by ZTE. If no patch is available, implement strict input validation on all user-controlled parameters in the web management interface.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-3417 — 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-2019-3417 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