CVE-2019-14458
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 allow a denial of service 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 denial-of-service vulnerability that can be triggered by sending a specially crafted HTTP header to the device. The vulnerability allows an unauthenticated remote attacker to crash the camera service or render the device unresponsive.
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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 device web interface or check device labeling/serial number to verify the device manufacturer and model is VIVOTEKAffected if The device is a VIVOTEK IP camera
-
Determine the installed firmware versionLog into the camera web interface and navigate to the firmware or system information page, or use the camera's CLI if available, to retrieve the current firmware version numberAffected if The firmware version is below 0x20x (versions prior to the 0x20x release)
-
Verify the firmware version notationCheck whether the version displays as hexadecimal format (0x prefix) or decimal format - the 0x20x notation indicates hexadecimal versioning where 0x20x translates to versions like 0x200, 0x201, etc.Affected if The firmware version cannot be confirmed as 0x20x or higher
-
Assess network exposure of the HTTP serviceDetermine if the camera HTTP management interface is accessible from untrusted networks - the vulnerability is exploitable by an unauthenticated remote attacker sending crafted HTTP headersAffected if The camera HTTP interface is exposed to untrusted networks AND firmware is below 0x20x
The environment is affected if the device is a VIVOTEK IP camera running firmware versions prior to 0x20x with its HTTP management interface accessible to potential attackers.
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 dataUpgrade VIVOTEK IP camera firmware to version 0x20x or later. As a compensating control, restrict network access to camera management interfaces using firewalls or VLANs to limit exposure to untrusted networks.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-14458 — 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-14458 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