CVE-2023-4465: Poly VVX 601 Configuration File Import unverified password change
Noroxi assessment
Priority: Monitor (action score 26/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.46% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
- Severity is disputed: the assigning authority (CNA) scores it 2.7, NVD 6.5.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Dec 29, 2023
- Updated
- Jun 17, 2026
- EPSS
- 0.4% · 40th percentile
- CWE
- CWE-620
Report tools
Action score
26
Monitor
Low priority for now.
- CVSS
- 26 / 40 · 6.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CNA vs NVD score
- NVD
- 6.5
- CNA · VulDB
- 2.7
- 3.8 point gap
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| poly | ccx 400 firmware | cpe:2.3:o:poly:ccx_400_firmware |
| poly | ccx 400 | cpe:2.3:h:poly:ccx_400 |
| poly | ccx 600 firmware | cpe:2.3:o:poly:ccx_600_firmware |
| poly | ccx 600 | cpe:2.3:h:poly:ccx_600 |
| poly | trio 8800 firmware | cpe:2.3:o:poly:trio_8800_firmware |
| poly | trio 8800 | cpe:2.3:h:poly:trio_8800 |
| poly | trio c60 firmware | cpe:2.3:o:poly:trio_c60_firmware |
| poly | trio c60 | cpe:2.3:h:poly:trio_c60 |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- poly ccx 400 firmwareall versions
- poly ccx 600 firmwareall versions
- poly trio 8800 firmwareall versions
- poly trio c60 firmwareall versions
Versions reported by the vendor
Affected version ranges reported by the assigning authority (VulDB). Independent of NVD's CPE analysis and usually ahead of it.
Poly CCX 350
- n/aaffected
Poly CCX 400
- n/aaffected
Poly CCX 500
- n/aaffected
Poly CCX 505
- n/aaffected
Poly CCX 600
- n/aaffected
Poly CCX 700
- n/aaffected
Poly EDGE E100
- n/aaffected
Poly EDGE E220
- n/aaffected
Poly EDGE E300
- n/aaffected
Poly EDGE E320
- n/aaffected
Poly EDGE E350
- n/aaffected
Poly EDGE E400
- n/aaffected
Same product
poly: all recordsOther highest-scoring records for the same primary product.
- CVE-2023-4463Poly CCX 400/CCX 600/Trio 8800/Trio C60 HTTP Header denial of service30Monitor
- CVE-2023-4464Poly VVX 601 Diagnostic Telnet Mode os command injection29Monitor
- CVE-2023-4462Poly VVX 601 Web Configuration Application random values23Monitor
Published before and after this one in the same product
- Later →CVE-2023-4466Dec 29, 2023 · Poly CCX 400/CCX 600/Trio 8800/Trio C60 Web Interface protection mechanism19Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Christoph Wolfffinder
- Pascal Zenkerfinder
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
CWE-620 · Unverified Password ChangeCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Show all references (5 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.