dbcve.org
Arrayos AgOperating system · Arraynetworks

CVE-2023-51707

CRITICAL · 9.8 CVSS v3.1 Published 2023-12-22
Fix available
A fix is available. Upgrade to 9.4.0.505 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
MotionPro in Array ArrayOS AG before 9.4.0.505 on AG and vxAG allows remote command execution via crafted packets. AG and vxAG 9.3.0.259.x are unaffected.

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

MotionPro client software in Array Networks AG and vxAG appliances before version 9.4.0.505 contains a pre-authentication remote command execution vulnerability exploitable via specially crafted network packets. The vulnerability resides in the MotionPro component and allows attackers to execute arbitrary commands on the affected system without authentication.

MitigationUpgrade Array Networks AG and vxAG appliances to version 9.4.0.505 or later. Note that version 9.3.0.259.x is explicitly unaffected by this vulnerability.

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
Arrayos AgOperating system
Affected:< 9.4.0.505

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 Array Networks appliance model
    Access the appliance admin interface or check system documentation to confirm whether the device is an Array Networks AG or vxAG appliance.
    Affected if The device is an Array Networks AG or vxAG appliance.
  2. Determine the firmware or software version
    Log into the appliance admin console and navigate to the system status or version information page. Alternatively, run the command 'show system' or 'get version' via CLI if accessible.
    Affected if The displayed version is below 9.4.0.505.
  3. Confirm the MotionPro component is present
    Check the appliance configuration or running services for the MotionPro component. This may be visible in the admin interface under 'Services' or 'Modules', or via CLI commands such as 'show motionpro status'.
    Affected if MotionPro is installed and running on the appliance.
  4. Verify MotionPro network exposure
    Check if the MotionPro service is listening on network interfaces exposed to untrusted networks. Review firewall rules or port listings (e.g., netstat output) for MotionPro ports.
    Affected if MotionPro is accessible from untrusted networks without authentication barriers.

The environment is affected if the device is an Array Networks AG or vxAG appliance running MotionPro with a firmware or software version below 9.4.0.505.

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 9.4.0.505 or later
Fixed in 9.4.0.505
Interim mitigation

Upgrade Array Networks AG and vxAG appliances to version 9.4.0.505 or later. Note that version 9.3.0.259.x is explicitly unaffected by this vulnerability.

Recommended fix High confidence

ArrayOS AG 9.4.0.505 or later

  1. Identify the current ArrayOS AG version by checking the device management interface or running 'show version'
  2. Download ArrayOS AG version 9.4.0.505 or later from support.arraynetworks.net
  3. Review upgrade instructions in the Array Networks admin guide
  4. Apply the upgrade during a maintenance window as per standard change management procedures
  5. After upgrade, verify the new version is installed with 'show version'
  6. Confirm the MotionPro service is running correctly post-upgrade
Caveat Standard network appliance upgrade risks apply - test in staging environment first

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

Fix this in Arrayos Ag Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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