{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2023-47257 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-47257 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-47257 is a high-severity code injection vulnerability in n/a, published on 1 Feb 2024. 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-47257 and fix it if it is affected.\n\nWhat it is: CVE-2023-47257 is a high-severity code injection vulnerability in n/a, published on 1 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-47257 in the wild and no public exploit code.\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-47257/ (Markdown: https://insights.sbomify.com/CVE-2023-47257/index.md)","id":"CVE-2023-47257","markdown":"https://insights.sbomify.com/CVE-2023-47257/index.md","name":"CVE-2023-47257","record":{"aliases":["GHSA-4ghr-47h5-v2hf"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Remote access software","requires_auth":"none","summary":"Man-in-the-middle attackers can achieve remote code execution in ConnectWise ScreenConnect by sending crafted messages.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"automate","vendor":"connectwise"},{"product":"screenconnect","vendor":"connectwise"}],"cvss":{"score":8.1,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"}],"description":"ConnectWise ScreenConnect through 23.8.4 allows man-in-the-middle attackers to achieve remote code execution via crafted messages.","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":"Code injection in n/a","id":"CVE-2023-47257","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2023-47258"},"packages":[],"prev":{"headline":"Security feature bypass in n/a","id":"CVE-2023-47256"},"products":["n/a"],"published":"2024-02-01","related":[{"cvss_score":9.8,"headline":"XML external entity in n/a","id":"CVE-2021-35066","kev_date_added":null,"published":"2021-06-21"},{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2020-15027","kev_date_added":null,"published":"2020-07-16"},{"cvss_score":9.6,"headline":"HTTP Configuration and Encryption in Transit","id":"CVE-2025-11492","kev_date_added":null,"published":"2025-10-16"},{"cvss_score":8.8,"headline":"Supply chain in Automate","id":"CVE-2026-9089","kev_date_added":null,"published":"2026-05-21"},{"cvss_score":8.8,"headline":"Self-Update Verification Mechanism Process in ConnectWise Automate","id":"CVE-2025-11493","kev_date_added":null,"published":"2025-10-16"},{"cvss_score":8.8,"headline":"Privilege escalation in n/a","id":"CVE-2020-15838","kev_date_added":null,"published":"2020-10-09"}],"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":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-05-07","vendors":["n/a"]},"summary":"Man-in-the-middle attackers can achieve remote code execution in ConnectWise ScreenConnect by sending crafted messages.","url":"https://insights.sbomify.com/CVE-2023-47257/"}