CVE-2019-14457
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 IP Camera devices with firmware before 0x20x have a stack-based buffer overflow via a crafted HTTP header.
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 IP cameras running firmware versions prior to 0x20x contain a stack-based buffer overflow vulnerability in their web server component. The vulnerability is triggered by sending a crafted HTTP header with excessive data, causing the camera to overflow a fixed-size stack buffer when copying the header value. This can potentially allow remote unauthenticated attackers to execute arbitrary code on the affected 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 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/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.
-
Confirm device is a VIVOTEK IP cameraAccess the camera's web interface and check the model information, or use network scanning/ONVIF to identify the device make and modelAffected if Device is not a VIVOTEK IP camera (not affected)
-
Check firmware versionLog into the camera's web interface and navigate to System > Information to view the firmware version, or query the camera via ONVIF or manufacturer's APIAffected if Firmware version is prior to 0x20x (vulnerable to this CVE)
-
Verify web server component is activeAttempt to access the camera's HTTP (port 80) or HTTPS (port 443) interface using a web browser or curl commandAffected if Web server is accessible and responding on HTTP/HTTPS ports (exposes the vulnerable component)
-
Confirm version thresholdCompare the identified firmware version against 0x20x - versions with prefix less than 20 (such as xx06, xx12, xx19) are affected, while versions starting with 20 or higher are notAffected if Installed version is below 0x20x and web server is reachable
A VIVOTEK IP camera is affected if it is running firmware version prior to 0x20x and has its web server interface accessible on the network.
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 VIVOTEK IP camera firmware to version 0x20x or later. If immediate patching is not feasible, restrict network access to the camera's HTTP/HTTPS services using firewall rules or network segmentation to limit exposure to trusted networks only.
- 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-2019-14457 — 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-14457 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