dbcve.org
Video Insight VmsApplication · Panasonic

CVE-2019-5997

CRITICAL · 9.8 CVSS v3.1 Published 2020-05-20
Fix available
A fix is available. Upgrade to after 7.5 or later.
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
Video Insight VMS versions prior to 7.6.1 allow remote attackers to conduct code injection attacks via unspecified vectors.

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

Video Insight VMS (Video Management Software) versions prior to 7.6.1 contain a code injection vulnerability with a critical CVSS score of 9.8. The vulnerability is remotely exploitable without authentication and allows attackers to inject arbitrary code, likely through insufficient input validation in unspecified user-facing interfaces.

MitigationUpgrade Video Insight VMS to version 7.6.1 or later to remediate the code injection vulnerability. Given the critical severity and remote exploitability, prioritize this upgrade immediately and restrict network access to the VMS until patched.

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
Video Insight VmsApplication
Affected:<= 7.5

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. Verify Video Insight VMS is installed
    Check for Video Insight VMS service or application on the system. Look for the Video Insight service in Windows Services or check for the installation directory.
    Affected if Video Insight VMS software is found on the system
  2. Determine the installed version
    Access the Video Insight VMS client or admin interface and navigate to the About or System Information section to find the software version. Alternatively, check the Windows Programs and Features list for the installed version.
    Affected if The displayed version number is 7.5 or lower (e.g., 7.5, 7.4, 7.3, etc.)
  3. Compare against affected version range
    The affected range is version 7.5 and below. If your installed version is 7.6.1 or higher, you are not in the affected range. If it is 7.5 or any version below 7.5, you are within the affected range.
    Affected if Installed version is 7.5 or lower, or the version cannot be determined (assume affected)
  4. Assess network exposure
    Since this vulnerability is remotely exploitable without authentication, check if the Video Insight VMS web interface or remote ports are accessible from untrusted networks. Review firewall rules and network segmentation.
    Affected if The VMS interface is exposed to the internet or untrusted internal networks

If Video Insight VMS is installed and the version is 7.5 or lower (or cannot be verified), and the interface is network-accessible, the environment is affected by this code injection 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
Upgrade available Upgrade to a release after 7.5
Interim mitigation

Upgrade Video Insight VMS to version 7.6.1 or later to remediate the code injection vulnerability. Given the critical severity and remote exploitability, prioritize this upgrade immediately and restrict network access to the VMS until patched.

Recommended fix High confidence

7.6.1 or later (latest stable release recommended)

  1. 1. Check the current Video Insight VMS version by accessing the server admin interface or checking the software About section
  2. 2. Backup all Video Insight VMS configuration data, databases, and recordings according to standard backup procedures
  3. 3. Download Video Insight VMS version 7.6.1 or later from the official vendor source (downloadvi.com)
  4. 4. Stop the Video Insight VMS services on the server before upgrading
  5. 5. Install the upgrade by running the installer with appropriate administrator privileges
  6. 6. Follow the on-screen upgrade wizard prompts to complete the installation
  7. 7. After installation, verify the new version is 7.6.1 or higher in the admin interface
  8. 8. Restart Video Insight VMS services and verify all cameras and recording functions are operational

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

Fix this in Video Insight Vms Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-5997 — 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-5997 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