# CVE-2023-34312: Memory corruption in n/a

> Attackers can exploit a write-what-where condition in Tencent QQ to execute arbitrary code or escalate privileges via IPC.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Jun 2023
- **Updated:** 9 Jan 2025
- **Also known as:** GHSA-hcp2-8j7p-77m4

## What is CVE-2023-34312?

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.

### Official 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.

Weakness: CWE-763 (Release of Invalid Pointer or Reference)

## Which versions are affected by CVE-2023-34312?

It affects 2 products.


Products: Tencent Qq, Tencent Tim.

## How do I fix CVE-2023-34312?

No fix has been published for CVE-2023-34312 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-34312 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-34312 exists.

Public exploit code:

- CVE-2023-34312 (github_poc): https://github.com/vi3t1/qq-tim-elevation
- 复现CVE-2023-34312所需的两个恶意dll文件 (github_poc): https://github.com/lan1oc/CVE-2023-34312-exp

## Other vulnerabilities in n/a

- [CVE-2021-33057](https://insights.sbomify.com/CVE-2021-33057/): Missing authorization in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-34312 and fix it if it is affected.

What 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-34312 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-34312/ (Markdown: https://insights.sbomify.com/CVE-2023-34312/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-34312
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-34312
- OSV: https://osv.dev/vulnerability/CVE-2023-34312

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-34312/
Summaries are generated and may contain mistakes; the official description above is the record.