XprotectApplication · Milestonesys

CVE-2018-7891

HIGH · 8.1 CVSS v3.0 Published 2018-04-30
Fix available
A fix is available. Upgrade to 10.0a / 10.1a or later.
See remediation →
90/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
The Milestone XProtect Video Management Software (Corporate, Expert, Professional+, Express+, Essential+) 2016 R1 (10.0.a) to 2018 R1 (12.1a) contains .NET Remoting endpoints that are vulnerable to deserialization attacks resulting in remote code execution.

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

Milestone XProtect Video Management Software versions 10.0a through 12.1a contain vulnerable .NET Remoting endpoints that accept deserialized data without proper validation, allowing attackers to execute arbitrary code remotely by sending crafted serialized objects.

MitigationUpdate to a patched version of XProtect that addresses this vulnerability. If immediate patching is not feasible, disable or restrict access to .NET Remoting endpoints and implement network segmentation to limit exposure.

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
XprotectApplication
Affected:>= 10.0.a, <= 12.1a
Siveillance VmsApplication
Affected:< 10.0a< 10.1a< 10.2b< 11.1a< 11.2a< 12.1a

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:H/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 installed XProtect or Siveillance VMS version
    Check the software version through the application UI (Help > About) or Windows Programs and Features, or use the Milestone Configuration Manager tool if available
    Affected if The version is between 10.0a and 12.1a inclusive for XProtect, or matches the affected Siemens Siveillance VMS version ranges (< 10.0a, < 10.1a, < 10.2b, < 11.1a, < 11.2a, < 12.1a)
  2. Confirm .NET Remoting is enabled
    Examine the XProtect installation for .NET Remoting service components. Check Windows services list for Remoting-related services, or inspect the XProtect server configuration files for Remoting endpoint definitions (typically found in installation directory config files)
    Affected if The .NET Remoting endpoints are actively enabled and the service is running
  3. Verify network exposure of Remoting ports
    Use netstat or a port scanner to identify listening ports associated with .NET Remoting (commonly TCP ports in the 5000-65000 range). Check firewall rules to determine if these ports are accessible from untrusted networks
    Affected if The .NET Remoting ports are listening and accessible from network segments outside the trusted management network
  4. Check for suspicious inbound connections
    Review Windows Event Logs (Security, Application) and any available network logs for inbound connections to Remoting ports, particularly from external IP addresses or during unusual hours
    Affected if There are unexpected inbound connections to Remoting endpoints from untrusted sources

You are affected if you are running a vulnerable XProtect version (10.0a through 12.1a) or an affected Siemens Siveillance VMS version AND the .NET Remoting feature is enabled and network-accessible.

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.

From vendor data
Upgrade available Upgrade to 10.0a / 10.1a / 10.2b or later
Fixed in 10.0a10.1a10.2b
Interim mitigation

Update to a patched version of XProtect that addresses this vulnerability. If immediate patching is not feasible, disable or restrict access to .NET Remoting endpoints and implement network segmentation to limit exposure.

Fix this in Xprotect Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-7891 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-7891 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