dbcve.org
Ccx 400 FirmwareOperating system · Poly

CVE-2023-4465

MEDIUM · 6.5 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 →
71/100
Remediation priority · Elevated
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 problematic, was 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. Affected is an unknown function of the component Configuration File Import. The manipulation of the argument device.auth.localAdminPassword leads to unverified password change. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. VDB-249258 is the identifier 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 vulnerability in Poly Trio, CCX, EDGE, and VVX phone devices allows unauthenticated manipulation of the device.auth.localAdminPassword argument during configuration file import, enabling an attacker to change the administrator password without verification and gain unauthorized administrative access to the device.

MitigationRestrict network access to device management interfaces, disable unused configuration import features, and apply vendor security updates when available.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

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 device model
    Access the device web interface or check the device label to confirm the exact model number (CCX 400, CCX 600, Trio 8800, or Trio C60)
    Affected if Device is one of these four models: CCX 400, CCX 600, Trio 8800, or Trio C60 - all versions are affected
  2. Verify configuration import feature is enabled
    Check the device web interface under Settings > Provisioning or Configuration > Import. Look for any configuration import/upload functionality that allows loading XML or config files
    Affected if Configuration import feature is enabled and accessible (even from internal network)
  3. Check for unauthorized admin account changes
    Review device admin settings in the web interface under Administration > Security or User Management. Compare the current localAdminPassword setting against known-good baseline documentation
    Affected if Local administrator password was changed without documented authorization or differs from expected baseline
  4. Inspect configuration file for suspicious localAdminPassword entries
    If configuration backup files exist on the device or in network traces, examine imported XML files for device.auth.localAdminPassword arguments with unexpected or changed password values
    Affected if Configuration files contain device.auth.localAdminPassword with a value that was not intentionally set by legitimate administrators
  5. Review device audit or event logs
    Check device logs for entries indicating configuration import operations, especially from unexpected IP addresses or occurring outside maintenance windows
    Affected if Configuration import events appear in logs without corresponding authorized change tickets or from unexpected sources

A user is affected if they operate any Poly CCX 400, CCX 600, Trio 8800, or Trio C60 device with configuration import functionality enabled, and unauthorized password changes or configuration imports are detected.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict network access to device management interfaces, disable unused configuration import features, and apply vendor security updates when available.

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-4465 — 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-4465 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