dbcve.org
Mirasys VmsApplication · Mirasys

CVE-2019-11031

CRITICAL · 9.8 CVSS v3.0 Published 2019-08-22
Fix available
A fix is available. Upgrade to 7.6.1 / 8.3.2 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
Mirasys VMS before V7.6.1 and 8.x before V8.3.2 mishandles the auto-update feature of IDVRUpdateService2 in DVRServer.exe. An attacker can upload files with a Setup-Files action, and then execute these files with SYSTEM privileges.

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 · high confidence

Mirasys VMS contains a vulnerability in the auto-update feature of IDVRUpdateService2 within DVRServer.exe. An unauthenticated or authenticated attacker can upload arbitrary files using the Setup-Files action and subsequently execute those files with SYSTEM-level privileges, achieving full remote code execution with highest Windows privileges.

MitigationUpgrade Mirasys VMS to version V7.6.1, V8.3.2, or later to resolve the vulnerability. If immediate patching is not feasible, implement network segmentation to restrict access to the DVRServer.exe service and disable the auto-update feature until upgrade can be completed.

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
Mirasys VmsApplication
Affected:< 7.6.1>= 8.0.0, < 8.3.2

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.0/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 Mirasys VMS installation path
    Locate DVRServer.exe on the system - typically found in the Mirasys installation directory (commonly C:\Program Files\Mirasys\ or C:\Mirasys\). Use file explorer or command: dir /s C:\*DVRServer.exe
    Affected if DVRServer.exe exists on the system and the version is below 7.6.1 or between 8.0.0 and 8.3.2
  2. Determine installed Mirasys VMS version
    Right-click DVRServer.exe, select Properties, then view the Details tab for version information. Alternatively, check the software version in Windows Programs and Features (Add/Remove Programs)
    Affected if The version displayed is < 7.6.1 or >= 8.0.0 but < 8.3.2
  3. Verify IDVRUpdateService2 component status
    Check if DVRServer.exe is running as a service. Open Services console (services.msc) and look for a Mirasys-related service, or run tasklist | findstr DVRServer from command prompt
    Affected if DVRServer.exe service is running and the version falls within the affected range
  4. Confirm auto-update feature configuration
    Inspect the configuration files in the Mirasys installation directory for update-related settings. Look for XML or config files containing 'Update', 'AutoUpdate', or 'IDVRUpdateService2' settings. Check if update functionality is enabled
    Affected if The auto-update feature is enabled and the installed version is within the vulnerable range

A system is affected if Mirasys VMS is installed with DVRServer.exe version < 7.6.1 or >= 8.0.0 and < 8.3.2, and the IDVRUpdateService2 auto-update feature is present and enabled.

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 7.6.1 / 8.3.2 or later
Fixed in 7.6.18.3.2
Interim mitigation

Upgrade Mirasys VMS to version V7.6.1, V8.3.2, or later to resolve the vulnerability. If immediate patching is not feasible, implement network segmentation to restrict access to the DVRServer.exe service and disable the auto-update feature until upgrade can be completed.

Recommended fix High confidence

For 7.x branch: upgrade to 7.6.1 or later; For 8.x branch: upgrade to 8.3.2 or later

  1. 1. Identify the current installed version of Mirasys VMS by checking the DVRServer.exe version or system information
  2. 2. If running version 7.x and below 7.6.1, plan upgrade to version 7.6.1 or later
  3. 3. If running version 8.x and below 8.3.2, plan upgrade to version 8.3.2 or later
  4. 4. Before upgrading, backup all configuration files and databases as a precaution
  5. 5. Download the appropriate fixed version from the vendor's official source (contact Mirasys or authorized resellers)
  6. 6. Schedule maintenance window as upgrade may require service interruption
  7. 7. Execute the upgrade following vendor-provided installation documentation
  8. 8. After upgrade, verify the IDVRUpdateService2 component is updated and the auto-update feature is properly secured
Caveat Review release notes for any configuration changes or migration requirements between versions; test upgrade in non-production environment first

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

Fix this in Mirasys Vms Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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