{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-39150 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-39150 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-39150 is a critical code injection vulnerability in n/a, published on 12 Sep 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-39150 and fix it if it is affected.\n\nWhat it is: CVE-2023-39150 is a critical code injection vulnerability in n/a, published on 12 Sep 2023. 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-39150 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-39150/ (Markdown: https://insights.sbomify.com/CVE-2023-39150/index.md)","id":"CVE-2023-39150","markdown":"https://insights.sbomify.com/CVE-2023-39150/index.md","name":"CVE-2023-39150","record":{"aliases":[],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"ConEmu terminal emulator","requires_auth":"none","summary":"Attackers can execute arbitrary code via unsanitized title responses in ConEmu, requiring a patch to mitigate the risk.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"conemu","vendor":"maximus5"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"ConEmu before commit 230724 does not sanitize title responses correctly for control characters, potentially leading to arbitrary code execution. This is related to an incomplete fix for CVE-2022-46387.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Code injection in n/a","id":"CVE-2023-39150","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":"Jenkins Stored Cross-site Scripting vulnerability","id":"CVE-2023-39151"},"packages":[],"prev":{"headline":"File upload in n/a","id":"CVE-2023-39147"},"products":["n/a"],"published":"2023-09-12","related":[],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-09-26","vendors":["n/a"]},"summary":"Attackers can execute arbitrary code via unsanitized title responses in ConEmu, requiring a patch to mitigate the risk.","url":"https://insights.sbomify.com/CVE-2023-39150/"}