CVE-2018-14770
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 · uneditedVIVOTEK FD8177 devices before XXXXXX-VVTK-xx06a allow remote attackers to execute arbitrary code (issue 1 of 2) via the ONVIF interface, (/onvif/device_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 · moderate confidenceVIVOTEK FD8177 IP cameras contain a remote code execution vulnerability in their ONVIF device service endpoint (/onvif/device_service). Attackers can send specially crafted SOAP requests to this web service interface to execute arbitrary commands on the underlying Linux-based firmware. The vulnerability affects devices running firmware versions prior to the patched release.
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 dataall versionsCVSS 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 device modelAccess the camera's web interface or check the device label/metadata to confirm the model is a VIVOTEK FD8177 IP camera. This can also be done via ONVIF probe or by checking HTTP headers from the device.Affected if The device is a VIVOTEK FD8177 IP camera and the firmware has not been updated to the vendor-patched version.
-
Verify ONVIF service availabilityAttempt to access the ONVIF device service endpoint at http://<camera_ip>/onvif/device_service or send a SOAP request to this endpoint. A successful response indicates the ONVIF service is running.Affected if The ONVIF device service endpoint responds to requests, meaning the ONVIF interface is enabled and accessible.
-
Check firmware versionLog into the camera web interface and navigate to the system information or firmware version page. Alternatively, use ONVIF GetDeviceInformation request or check VIVOTEK's release notes for the patched firmware version.Affected if The camera is running firmware version prior to the vendor-patched release for CVE-2018-14770.
-
Assess network exposureDetermine if the ONVIF service port (typically 8080 or 80) is accessible from untrusted networks. Use network scanning tools or review firewall rules to check if the camera's ONVIF endpoint is exposed to the internet or untrusted VLANs.Affected if The ONVIF service is reachable from untrusted network segments or the internet without access controls.
A user is affected if they have a VIVOTEK FD8177 camera with an accessible ONVIF device service running firmware prior to the patched version, particularly if the service 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 dataPrimary mitigation is to update the device firmware to the vendor-patched version. If firmware updates are unavailable, restrict network access to the ONVIF service by placing cameras in isolated network segments or implementing firewall rules to limit access to trusted IP addresses only.
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-14770 — 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-14770 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