Tencent QQ/TIM Inter-Process Communication QQProtect.exe write-what-where condition

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
7.0$0-$5k0.00

Summaryinfo

A vulnerability marked as problematic has been reported in Tencent QQ and TIM. This vulnerability affects unknown code in the library QQProtectEngine.dll of the file QQProtect.exe of the component Inter-Process Communication. Performing a manipulation results in write-what-where condition. This vulnerability is cataloged as CVE-2023-34312. There is no exploit available.

Detailsinfo

A vulnerability classified as problematic has been found in Tencent QQ and TIM (the affected version is unknown). This affects an unknown code in the library QQProtectEngine.dll of the file QQProtect.exe of the component Inter-Process Communication. The manipulation with an unknown input leads to a write-what-where condition vulnerability. CWE is classifying the issue as CWE-123. Any condition where the attacker has the ability to write an arbitrary value to an arbitrary location, often as the result of a buffer overflow. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

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.

The weakness was shared 06/01/2023. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2023-34312 since 06/01/2023. Technical details are known, but no exploit is available.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2023-38393). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

Name

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.0
VulDB Meta Temp Score: 7.0

VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 7.8
NVD Vector: 🔍

CNA Base Score: 7.8
CNA Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

Exploitinginfo

Class: Write-what-where condition
CWE: CWE-123 / CWE-119
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: Partially

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

06/01/2023 🔍
06/01/2023 +0 days 🔍
06/01/2023 +0 days 🔍
01/07/2026 +951 days 🔍

Sourcesinfo

Advisory: github.com
Status: Not defined

CVE: CVE-2023-34312 (🔍)
GCVE (CVE): GCVE-0-2023-34312
GCVE (VulDB): GCVE-100-230409
EUVD: 🔍

Entryinfo

Created: 06/01/2023 06:22
Updated: 01/07/2026 08:34
Changes: 06/01/2023 06:22 (38), 06/25/2023 12:47 (11), 01/09/2025 22:18 (26), 01/07/2026 08:34 (1)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to know what is going to be exploited?

We predict KEV entries!