{"answers":{"affected":"It affects 6 products.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-22957 exists.","fix":"No fix has been published for CVE-2023-22957 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-22957 is a high-severity vulnerability in n/a, published on 11 Aug 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-22957 and fix it if it is affected.\n\nWhat it is: CVE-2023-22957 is a high-severity vulnerability in n/a, published on 11 Aug 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-22957 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-22957/ (Markdown: https://insights.sbomify.com/CVE-2023-22957/index.md)","id":"CVE-2023-22957","markdown":"https://insights.sbomify.com/CVE-2023-22957/index.md","name":"CVE-2023-22957","record":{"aliases":["GHSA-6v2p-6369-885j"],"analysis":{"component_type":"iot_embedded","fix_type":"upgrade","impacts":["data_read","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"VoIP desk phone","requires_auth":"none","summary":"Attackers with access to backup files can decrypt sensitive data using a hard-coded key, potentially retrieving the device root password.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"405hd_firmware","vendor":"audiocodes"},{"product":"445hd_firmware","vendor":"audiocodes"},{"product":"c435hd_firmware","vendor":"audiocodes"},{"product":"c450hd_firmware","vendor":"audiocodes"},{"product":"c455hd_firmware","vendor":"audiocodes"},{"product":"c470hd_firmware","vendor":"audiocodes"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"}],"description":"An issue was discovered in libac_des3.so on AudioCodes VoIP desk phones through 3.4.4.1000. Due to the use of hard-coded cryptographic key, an attacker with access to backup or configuration files is able to decrypt encrypted values and retrieve sensitive information, e.g., the device root password.","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":"Hardcoded credentials in n/a","id":"CVE-2023-22957","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2023"},"n_packages":0,"n_references":4,"next":{"headline":"Open redirect in n/a","id":"CVE-2023-22958"},"packages":[],"prev":{"headline":"Hardcoded credentials in n/a","id":"CVE-2023-22956"},"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.8,"headline":"Security feature bypass in n/a","id":"CVE-2023-22955","kev_date_added":null,"published":"2023-08-11"},{"cvss_score":7.5,"headline":"Hardcoded credentials in n/a","id":"CVE-2023-22956","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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-10-10","vendors":["n/a"]},"summary":"Attackers with access to backup files can decrypt sensitive data using a hard-coded key, potentially retrieving the device root password.","url":"https://insights.sbomify.com/CVE-2023-22957/"}