dbcve.org
Ccx 400 FirmwareOperating system · Poly

CVE-2023-4464

HIGH · 7.2 CVSS v3.1 Published 2023-12-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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
A vulnerability, which was classified as critical, has been found in Poly Trio 8300, Trio 8500, Trio 8800, Trio C60, CCX 350, CCX 400, CCX 500, CCX 505, CCX 600, CCX 700, EDGE E100, EDGE E220, EDGE E300, EDGE E320, EDGE E350, EDGE E400, EDGE E450, EDGE E500, EDGE E550, VVX 101, VVX 150, VVX 201, VVX 250, VVX 300, VVX 301, VVX 310, VVX 311, VVX 350, VVX 400, VVX 401, VVX 410, VVX 411, VVX 450, VVX 500, VVX 501, VVX 600 and VVX 601. This issue affects some unknown processing of the component Diagnostic Telnet Mode. The manipulation leads to os command injection. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. It is recommended to upgrade the affected component. The identifier VDB-249257 was assigned to this vulnerability.

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

A critical OS command injection vulnerability exists in the Diagnostic Telnet Mode of multiple Poly VoIP phones (Trio, CCX, EDGE, and VVX series). Attackers can remotely execute arbitrary operating system commands through the telnet diagnostic interface. A public exploit is available, increasing exploitation risk.

MitigationUpgrade all affected Poly devices to the latest firmware version. If patching is not immediately feasible, disable the Diagnostic Telnet Mode and restrict network access to these devices to limit attack surface.

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
Ccx 400 FirmwareOperating system
Affected:all versions
Ccx 600 FirmwareOperating system
Affected:all versions
Trio 8800 FirmwareOperating system
Affected:all versions
Trio C60 FirmwareOperating system
Affected:all versions

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

CVSS:3.1/AV:N/AC:L/PR:H/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 Poly VoIP device models on your network
    Access your network inventory or use network scanning (e.g., nmap, SNMP queries, or device management console) to discover Poly phones. Note the model numbers of all Poly devices present.
    Affected if The device model is CCX 400, CCX 600, Trio 8800, or Trio C60.
  2. Confirm device firmware version
    Log into the Poly device web interface (if available) or use the device management system to retrieve the current firmware version. Compare against the affected product list.
    Affected if The device is a CCX 400, CCX 600, Trio 8800, or Trio C60 running any firmware version (all versions are affected).
  3. Check if Telnet service is accessible
    From a trusted internal host, attempt a telnet connection to the device IP on port 23 (e.g., telnet <device_ip>). Alternatively, run a port scan: nmap -p 23 <device_ip>.
    Affected if Port 23/telnet responds and accepts connections, indicating the telnet service is active.
  4. Verify Diagnostic Telnet Mode status
    If telnet access is available, log in with administrative credentials and check the diagnostic mode configuration. On Poly devices, this is typically found under Settings > Diagnostics or through the hidden diagnostic menu accessible via specific key sequences or URLs. Consult device documentation for exact navigation.
    Affected if Diagnostic Telnet Mode is enabled and accessible, allowing command execution at the diagnostic prompt.

Your environment is affected if you have any Poly CCX 400, CCX 600, Trio 8800, or Trio C60 devices with Diagnostic Telnet Mode enabled and accessible on your 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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade all affected Poly devices to the latest firmware version. If patching is not immediately feasible, disable the Diagnostic Telnet Mode and restrict network access to these devices to limit attack surface.

Recommended fix Moderate confidence

Contact vendor for latest fixed firmware version

  1. Contact Poly/HP support directly to obtain the latest firmware version that addresses CVE-2023-4464
  2. Request specific firmware version information for your device models (CCX 400, CCX 600, Trio 8800, Trio C60)
  3. Apply the firmware update provided by Poly/HP support after validating it against the vulnerability
Caveat Ensure backup of configuration before firmware upgrade; some firmware updates may reset device settings

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

Fix this in Ccx 400 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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