{"answers":{"affected":"It affects 3 products.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-22955 exists.","fix":"No fix has been published for CVE-2023-22955 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-22955 is a high-severity vulnerability in n/a, published on 11 Aug 2023. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-22955 and fix it if it is affected.\n\nWhat it is: CVE-2023-22955 is a high-severity vulnerability in n/a, published on 11 Aug 2023. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-22955 exists.\n\nAffected product: n/a. 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-22955/ (Markdown: https://insights.sbomify.com/CVE-2023-22955/index.md)","id":"CVE-2023-22955","markdown":"https://insights.sbomify.com/CVE-2023-22955/index.md","name":"CVE-2023-22955","record":{"aliases":["GHSA-xjqg-wxv8-wvg6"],"analysis":{"component_type":"iot_embedded","fix_type":"patch","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"VoIP desk phone","requires_auth":"low_privilege","summary":"Attackers can bypass firmware validation on AudioCodes VoIP phones to install malicious firmware, enabling remote code execution.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"405hd_firmware","vendor":"audiocodes"},{"product":"445hd_firmware","vendor":"audiocodes"},{"product":"c450hd_firmware","vendor":"audiocodes"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-345","name":"Insufficient Verification of Data Authenticity"}],"description":"An issue was discovered on AudioCodes VoIP desk phones through 3.4.4.1000. The validation of firmware images only consists of simple checksum checks for different firmware components. Thus, by knowing how to calculate and where to store the required checksums for the flasher tool, an attacker is able to store malicious firmware.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Security feature bypass in n/a","id":"CVE-2023-22955","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2023"},"n_packages":0,"n_references":4,"next":{"headline":"Hardcoded credentials in n/a","id":"CVE-2023-22956"},"packages":[],"prev":{"headline":"Code injection in n/a","id":"CVE-2023-22953"},"products":["n/a"],"published":"2023-08-11","related":[{"cvss_score":8.8,"headline":"Auth bypass in n/a","id":"CVE-2018-16219","kev_date_added":null,"published":"2019-04-25"},{"cvss_score":8,"headline":"Command injection in n/a","id":"CVE-2018-16216","kev_date_added":null,"published":"2019-04-25"},{"cvss_score":7.5,"headline":"Hardcoded credentials in n/a","id":"CVE-2023-22956","kev_date_added":null,"published":"2023-08-11"},{"cvss_score":7.5,"headline":"Hardcoded credentials in n/a","id":"CVE-2023-22957","kev_date_added":null,"published":"2023-08-11"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2018-16220","kev_date_added":null,"published":"2019-04-25"}],"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":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-10-10","vendors":["n/a"]},"summary":"Attackers can bypass firmware validation on AudioCodes VoIP phones to install malicious firmware, enabling remote code execution.","url":"https://insights.sbomify.com/CVE-2023-22955/"}