dbcve.org
Maxpro Nvr Xe FirmwareOperating system · Honeywell

CVE-2020-6959

CRITICAL · 9.8 CVSS v3.1 Published 2020-01-22
Fix available
A fix is available. Upgrade to after 5.6 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 following versions of MAXPRO VMS and NVR, MAXPRO VMS:HNMSWVMS prior to Version VMS560 Build 595 T2-Patch, HNMSWVMSLT prior to Version VMS560 Build 595 T2-Patch, MAXPRO NVR: MAXPRO NVR XE prior to Version NVR 5.6 Build 595 T2-Patch, MAXPRO NVR SE prior to Version NVR 5.6 Build 595 T2-Patch, MAXPRO NVR PE prior to Version NVR 5.6 Build 595 T2-Patch, and MPNVRSWXX prior to Version NVR 5.6 Build 595 T2-Patch are vulnerable to an unsafe deserialization of untrusted data. An attacker may be able to remotely modify deserialized data without authentication using a specially crafted web request, 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

This is an unsafe deserialization vulnerability in MAXPRO VMS and NVR video surveillance systems. An unauthenticated attacker can send specially crafted web requests containing malicious serialized data that gets deserialized without proper validation, leading to arbitrary code execution on the affected system.

MitigationApply the vendor-provided patches: upgrade MAXPRO VMS (HNMSWVMS/HNMSWVMSLT) to VMS560 Build 595 T2-Patch or later, and upgrade MAXPRO NVR (all variants) to NVR 5.6 Build 595 T2-Patch or later.

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
Maxpro Nvr Xe FirmwareOperating system
Affected:<= 5.6
Maxpro Nvr Se FirmwareOperating system
Affected:<= 5.6
Maxpro Nvr Pe FirmwareOperating system
Affected:<= 5.6
Mpnvrswxx FirmwareOperating system
Affected:<= 5.6
Hnmswvms FirmwareOperating system
Affected:<= vms560
Hnmswvmslt FirmwareOperating system
Affected:<= vms560

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 the MAXPRO device type
    Access the device web interface or check system information. For NVR devices, look for 'Maxpro NVR Xe/Se/Pe' or 'Mpnvrswxx' in the system branding. For VMS servers, look for 'HNMSWVMS' or 'HNMSWVMSLT' in the product name.
    Affected if The device is any of: Maxpro NVR Xe, Maxpro NVR Se, Maxpro NVR Pe, Mpnvrswxx, HNMSWVMS, or HNMSWVMSLT.
  2. Determine the firmware version
    Log into the MAXPRO web interface and navigate to System > About or System > Information page. Alternatively, check the version displayed on the login page or in the system status. For NVR: look for 'Firmware Version' or 'Build'. For VMS: look for the software version number.
    Affected if The firmware version is 5.6 or lower for NVR variants (Xe/Se/Pe/Mpnvrswxx), or vms560 or lower for VMS variants (HNMSWVMS/HNMSWVMSLT).
  3. Verify web service is accessible
    Attempt to access the device web interface via HTTP/HTTPS on the typical ports (80, 443, 8080, or the configured web port). Confirm the MAXPRO login page or API endpoints respond.
    Affected if The web interface is accessible from the network where an attacker could send malicious requests.
  4. Check for evidence of exploitation attempts
    Review web server access logs and security event logs for patterns indicating deserialization attacks, such as unusual serialized data in POST requests, known Java deserialization payloads, or unexpected code execution events.
    Affected if Logs show suspicious requests containing serialized Java objects or known exploitation patterns.

You are affected if your device is a MAXPRO NVR (Xe/Se/Pe or Mpnvrswxx) with firmware <= 5.6, or a MAXPRO VMS (HNMSWVMS/HNMSWVMSLT) with firmware <= vms560, and the web interface is 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.

dbcve · scoped
Upgrade available Upgrade to a release after 5.6
Interim mitigation

Apply the vendor-provided patches: upgrade MAXPRO VMS (HNMSWVMS/HNMSWVMSLT) to VMS560 Build 595 T2-Patch or later, and upgrade MAXPRO NVR (all variants) to NVR 5.6 Build 595 T2-Patch or later.

Recommended fix High confidence

NVR products: NVR 5.6 Build 595 T2-Patch | VMS products: VMS560 Build 595 T2-Patch

  1. 1. Identify the specific MAXPRO product model (NVR XE, NVR SE, NVR PE, MPNVRSWXX, HNMSWVMS, or HNMSWVMSLT) currently deployed
  2. 2. Determine the current firmware version by accessing the device admin interface or checking system information
  3. 3. Download the appropriate patched firmware from the official Honeywell/MAXPRO vendor website or authorized support channels
  4. 4. For NVR products (XE, SE, PE, MPNVRSWXX): Upgrade to version NVR 5.6 Build 595 T2-Patch or later
  5. 5. For VMS products (HNMSWVMS, HNMSWVMSLT): Upgrade to version VMS560 Build 595 T2-Patch or later
  6. 6. Follow vendor instructions for firmware upload and installation via the web interface or management tool
  7. 7. After upgrade, verify the system is operational and confirm the new firmware version is applied
  8. 8. Validate that the vulnerability is no longer present by reviewing system logs and running any available security scans

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

Fix this in Maxpro Nvr Xe Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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