{"answers":{"affected":"It affects 2 products.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-34312 exists.","fix":"No fix has been published for CVE-2023-34312 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-34312 is a high-severity memory corruption vulnerability in n/a, published on 1 Jun 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-34312 and fix it if it is affected.\n\nWhat it is: CVE-2023-34312 is a high-severity memory corruption vulnerability in n/a, published on 1 Jun 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-34312 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-34312/ (Markdown: https://insights.sbomify.com/CVE-2023-34312/index.md)","id":"CVE-2023-34312","markdown":"https://insights.sbomify.com/CVE-2023-34312/index.md","name":"CVE-2023-34312","record":{"aliases":["GHSA-hcp2-8j7p-77m4"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Tencent QQ client","requires_auth":"low_privilege","summary":"Attackers can exploit a write-what-where condition in Tencent QQ to execute arbitrary code or escalate privileges via IPC.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"qq","vendor":"tencent"},{"product":"tim","vendor":"tencent"}],"cvss":{"score":7.8,"severity":"high","source":"cisa-adp","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-763","name":"Release of Invalid Pointer or Reference"}],"description":"In Tencent QQ through 9.7.8.29039 and TIM through 3.4.7.22084, QQProtect.exe and QQProtectEngine.dll do not validate pointers from inter-process communication, which leads to a write-what-where condition.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2023-05-27","github_poc":2,"max_poc_stars":417,"metasploit":0,"nuclei":0,"refs":[{"date":"2023-05-27T12:44:42Z","kind":"github_poc","ref":"https://github.com/vi3t1/qq-tim-elevation","stars":417,"title":"CVE-2023-34312"},{"date":"2023-08-07T13:09:11Z","kind":"github_poc","ref":"https://github.com/lan1oc/CVE-2023-34312-exp","stars":8,"title":"复现CVE-2023-34312所需的两个恶意dll文件"}],"tier":"weaponised"},"has_fix":null,"headline":"Memory corruption in n/a","id":"CVE-2023-34312","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused","id":"CVE-2023-34313"},"packages":[],"prev":{"headline":"Ashlar-Vellum Cobalt Untrusted Pointer Dereference Remote Code Execution Vulnerability","id":"CVE-2023-34311"},"products":["n/a"],"published":"2023-06-01","related":[{"cvss_score":7.5,"headline":"Missing authorization in n/a","id":"CVE-2021-33057","kev_date_added":null,"published":"2022-07-26"}],"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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-01-09","vendors":["n/a"]},"summary":"Attackers can exploit a write-what-where condition in Tencent QQ to execute arbitrary code or escalate privileges via IPC.","url":"https://insights.sbomify.com/CVE-2023-34312/"}