dbcve.org
Mirasys VmsApplication · Mirasys

CVE-2019-11030

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 Mirasys.Common.Utils.Security.DataCrypt method in Common.dll in AuditTrailService in SMServer.exe. This method triggers insecure deserialization within the .NET garbage collector, in which a gadget (contained in a serialized object) may be executed with SYSTEM privileges. The attacker must properly encrypt the object; however, the hardcoded keys are available.

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 versions before V7.6.1 and 8.x before V8.3.2 contain an insecure deserialization vulnerability in the DataCrypt method within Common.dll, used by the AuditTrailService in SMServer.exe. Attackers can exploit this by sending specially crafted, encrypted serialized .NET objects that execute with SYSTEM privileges due to gadget chains in the deserialization process. The hardcoded encryption keys make exploitation straightforward.

MitigationUpgrade Mirasys VMS to version V7.6.1 or later, or V8.3.2 or later. Prior to upgrade, implement network segmentation to limit SMServer.exe exposure and monitor for anomalous traffic to the AuditTrailService.

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 installed version
    Locate the Mirasys VMS installation directory and check the version information, typically found in the product's about or system information screen, or by inspecting version metadata of SMServer.exe
    Affected if The installed version is below 7.6.1, or is 8.x but below 8.3.2
  2. Verify SMServer.exe presence
    Confirm that SMServer.exe exists in the Mirasys installation directory, typically under the server or bin folder
    Affected if SMServer.exe is present and running
  3. Confirm AuditTrailService is enabled
    Check if the AuditTrailService is active and listening, typically via service status or network port inspection for the service endpoint
    Affected if AuditTrailService is running and network-accessible
  4. Check service privilege level
    Examine the account under which SMServer.exe or the AuditTrailService is running, typically via Windows Task Manager or Service Control Manager
    Affected if The service runs with SYSTEM or elevated administrator privileges
  5. Identify Common.dll version
    Locate Common.dll within the Mirasys installation directory and retrieve its file version metadata
    Affected if Common.dll is present and matches versions associated with vulnerable VMS releases

A user is affected if their Mirasys VMS version is less than 7.6.1 or falls between 8.0.0 and 8.3.2, and the AuditTrailService via SMServer.exe is accessible on the network.

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 or later, or V8.3.2 or later. Prior to upgrade, implement network segmentation to limit SMServer.exe exposure and monitor for anomalous traffic to the AuditTrailService.

Recommended fix High confidence

Mirasys VMS 7.6.1 (for 7.x branch) or Mirasys VMS 8.3.2 or later (for 8.x branch)

  1. Identify the current Mirasys VMS version by checking SMServer.exe or system information
  2. Determine which version branch is in use (7.x or 8.x)
  3. Backup all VMS configuration data, databases, and audit trail files before proceeding
  4. For 7.x versions: upgrade to VMS version 7.6.1 or later
  5. For 8.x versions: upgrade to VMS version 8.3.2 or later
  6. After upgrade, verify the Mirasys.Common.Utils.Security.DataCrypt method is updated in Common.dll
  7. Restart SMServer.exe and AuditTrailService
  8. Confirm the hardcoded encryption keys have been changed from defaults
Caveat Upgrading between major version branches (e.g., 7.x to 8.x) may require configuration migration; test in staging first

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

Fix this in Mirasys Vms Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,420
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,872.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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