{"answers":{"affected":"It affects 4 products.","exploited":"There is no known exploitation of CVE-2023-4466 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-4466 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-4466 is a low-severity vulnerability in Poly CCX 400, published on 29 Dec 2023. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-4466 and fix it if it is affected.\n\nWhat it is: CVE-2023-4466 is a low-severity vulnerability in Poly CCX 400, published on 29 Dec 2023. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-4466 in the wild and no public exploit code.\n\nAffected product: Poly CCX 400. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2023-4466/ (Markdown: https://insights.sbomify.com/CVE-2023-4466/index.md)","id":"CVE-2023-4466","markdown":"https://insights.sbomify.com/CVE-2023-4466/index.md","name":"CVE-2023-4466","record":{"aliases":["GHSA-38xw-jx8m-w5wp"],"analysis":{"component_type":"iot_embedded","fix_type":"configuration_change","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Poly conference phones","requires_auth":"high_privilege","summary":"Attackers can bypass protection mechanisms in Poly conference phone web interfaces, potentially enabling roll-back attacks to vulnerable firmware versions.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[{"product":"ccx_400_firmware","vendor":"poly"},{"product":"ccx_600_firmware","vendor":"poly"},{"product":"trio_8800_firmware","vendor":"poly"},{"product":"trio_c60_firmware","vendor":"poly"}],"cvss":{"score":2.7,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-693","name":"Protection Mechanism Failure"}],"description":"A vulnerability has been found in Poly CCX 400, CCX 600, Trio 8800 and Trio C60 and classified as problematic. Affected by this vulnerability is an unknown functionality of the component Web Interface. The manipulation leads to protection mechanism failure. The attack can be launched remotely. The vendor explains that they do not regard this as a vulnerability as this is a feature that they offer to their customers who have a variety of environmental needs that are met through different firmware builds. To avoid potential roll-back attacks, they remove vulnerable builds from the public servers as a remediation effort. The exploit has been disclosed to the public and may be used. The associated identifier of this vulnerability is VDB-249259.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Poly CCX 400/CCX 600/Trio 8800/Trio C60 Web Interface protection mechanism","id":"CVE-2023-4466","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2023"},"n_packages":0,"n_references":5,"next":{"headline":"Poly Trio 8800 Test Automation Mode backdoor","id":"CVE-2023-4467"},"packages":[],"prev":{"headline":"Poly VVX 601 Configuration File Import unverified password change","id":"CVE-2023-4465"},"products":["CCX 400","CCX 600","Trio 8800","Trio C60"],"published":"2023-12-29","related":[{"cvss_score":7.2,"headline":"Poly VVX 601 Diagnostic Telnet Mode os command injection","id":"CVE-2023-4464","kev_date_added":null,"published":"2023-12-29"},{"cvss_score":5.3,"headline":"Poly CCX 400/CCX 600/Trio 8800/Trio C60 HTTP Header denial of service","id":"CVE-2023-4463","kev_date_added":null,"published":"2023-12-29"},{"cvss_score":3.7,"headline":"Poly VVX 601 Web Configuration Application random values","id":"CVE-2023-4462","kev_date_added":null,"published":"2023-12-29"},{"cvss_score":2.7,"headline":"Poly VVX 601 Configuration File Import unverified password change","id":"CVE-2023-4465","kev_date_added":null,"published":"2023-12-29"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-02","vendors":["Poly"]},"summary":"Attackers can bypass protection mechanisms in Poly conference phone web interfaces, potentially enabling roll-back attacks to vulnerable firmware versions.","url":"https://insights.sbomify.com/CVE-2023-4466/"}