dbcve.org
CameraHardware / appliance · Vivotek

CVE-2019-10256

CRITICAL · 9.8 CVSS v3.1 Published 2019-09-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
An authentication bypass vulnerability in VIVOTEK IPCam versions prior to 0x13a was found.

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 confidence

VIVOTEK IP cameras running firmware versions prior to 0x13a contain an authentication bypass vulnerability that allows attackers to circumvent authentication mechanisms, potentially gaining unauthorized administrative access to the device without valid credentials.

MitigationUpdate VIVOTEK IP camera firmware to version 0x13a or later to remediate the authentication bypass vulnerability. If immediate patching is not possible, restrict network access to camera management interfaces using firewall rules or VLAN segmentation.

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
CameraHardware / appliance
Affected:all versions

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify VIVOTEK camera model
    Locate the device on the network and check its web interface, or use network scanning to identify the device manufacturer and model through HTTP headers, DHCP fingerprinting, or mDNS/Bonjour service banners that contain 'Vivotek' or 'VTC' in the identifier
    Affected if The device is not a VIVOTEK IP camera
  2. Determine firmware version
    Access the camera's web administration interface and navigate to System > System Information or similar firmware/version status page, or query the camera's CGI/API endpoint that exposes firmware version information if known
    Affected if Unable to retrieve firmware version from the device
  3. Compare firmware version to affected range
    Locate the firmware version string (typically displayed as a hexadecimal value like 0x##) in the system information page or banner, and compare it numerically to version 0x13a - any version value less than 0x13a indicates the device is running a vulnerable firmware version
    Affected if The installed firmware version is below 0x13a (e.g., 0x12f, 0x100, etc.)
  4. Verify authentication mechanism exposure
    Confirm the camera management interface is accessible from the network segment where untrusted users or systems can reach it, as the vulnerability allows remote authentication bypass without any prior access
    Affected if Camera administrative interface is accessible from an untrusted network segment and firmware is below 0x13a

If the device is a VIVOTEK IP camera running firmware version below 0x13a and its management interface is network-accessible, the environment is affected by this authentication bypass vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update VIVOTEK IP camera firmware to version 0x13a or later to remediate the authentication bypass vulnerability. If immediate patching is not possible, restrict network access to camera management interfaces using firewall rules or VLAN segmentation.

Recommended fix Low confidence

Firmware version 0x13a or later

  1. 1. Identify the specific VIVOTEK IP camera model in use
  2. 2. Access the camera's web interface or management console
  3. 3. Navigate to the firmware upgrade or system settings section
  4. 4. Download the firmware version 0x13a or later from download.vivotek.com or www.vivotek.com
  5. 5. Upload and apply the firmware update following the vendor's instructions
  6. 6. After upgrade, verify the camera is functioning properly and the firmware version reflects 0x13a or later

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Camera Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-10256 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-10256 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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