dbcve.org
Command ClientApplication · Marchnetworks

CVE-2019-9163

CRITICAL · 9.8 CVSS v3.1 Published 2020-04-01
Fix available
A fix is available. Upgrade to 2.7.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
The connection initiation process in March Networks Command Client before 2.7.2 allows remote attackers to execute arbitrary code via crafted XAML objects.

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

The March Networks Command Client versions prior to 2.7.2 contain a vulnerability in the connection initiation process where the application fails to properly validate XAML objects received during the connection handshake. Attackers can send specially crafted malicious XAML that gets parsed by the client, leading to arbitrary code execution on the affected system.

MitigationUpgrade March Networks Command Client to version 2.7.2 or later. If immediate patching is not possible, restrict network access to trusted servers only and disable the connection initiation feature until the upgrade can be applied.

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
Command ClientApplication
Affected:< 2.7.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.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 March Networks Command Client installation
    Open Windows Control Panel > Programs and Features, or check C:\Program Files\March Networks for the application directory. Look for 'Command Client' in the installed programs list.
    Affected if The application is installed on the system
  2. Determine installed version number
    Right-click the March Networks Command Client executable (typically CommandClient.exe), select Properties, and check the 'Version' tab. Alternatively, open the application and look in Help > About or Help > About Command Client.
    Affected if The version shown is earlier than 2.7.2 (for example, 2.7.1, 2.7.0, 2.6.x, etc.)
  3. Verify connection initiation feature usage
    Check if the client is configured to connect to remote March Networks servers. Look in the application settings, configuration files in the installation directory, or registry keys under HKEY_LOCAL_MACHINE\SOFTWARE\March Networks for server connection profiles.
    Affected if The client has server connection profiles configured or is set to automatically initiate connections to remote servers
  4. Confirm vulnerable configuration state
    Review any logs or configuration indicating the client has attempted or will attempt connections to servers. Check if the 'Auto-connect' or similar connection-on-startup feature is enabled in the client settings.
    Affected if The client is configured to automatically connect to servers or has active server connection settings configured

The system is affected if March Networks Command Client is installed with a version number lower than 2.7.2 and the client has server connection profiles or auto-connect features 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 2.7.2 or later
Fixed in 2.7.2
Interim mitigation

Upgrade March Networks Command Client to version 2.7.2 or later. If immediate patching is not possible, restrict network access to trusted servers only and disable the connection initiation feature until the upgrade can be applied.

Recommended fix Moderate confidence

Command Client 2.7.2 or later

  1. 1. Identify the current version of March Networks Command Client installed in your environment
  2. 2. Obtain the fixed version (2.7.2 or later) from the official March Networks support portal or vendor
  3. 3. Schedule a maintenance window for the upgrade
  4. 4. Backup the current installation and any associated configuration data
  5. 5. Deploy version 2.7.2 or later to all affected systems
  6. 6. Verify the upgrade was successful by checking the installed version
  7. 7. Test that the Command Client functionality is working as expected

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

Fix this in Command Client Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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