APUS Launcher 3.10.73/3.10.88 FONT_FILE privilege escalation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.9 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in APUS Launcher 3.10.73/3.10.88. Affected is an unknown function. Performing a manipulation of the argument FONT_FILE results in an unknown weakness. This vulnerability is identified as CVE-2023-27650. The attack can be initiated remotely. There is not any exploit available.
Details
A vulnerability was found in APUS Launcher 3.10.73/3.10.88. It has been classified as critical. The manipulation of the argument FONT_FILE with an unknown input leads to a unknown weakness. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
An issue found in APUS Group Launcher v.3.10.73 and v.3.10.88 allows a remote attacker to execute arbitrary code via the FONT_FILE parameter.
The weakness was released 04/10/2023. It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2023-27650 since 03/05/2023. Technical details of the vulnerability are known, but there is no available exploit.
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-31386). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.0VulDB Meta Temp Score: 7.9
VulDB Base Score: 6.3
VulDB Temp Score: 6.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Privilege escalationCWE: Unknown
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
03/05/2023 🔍04/10/2023 🔍
04/10/2023 🔍
11/19/2025 🔍
Sources
Advisory: github.comStatus: Not defined
CVE: CVE-2023-27650 (🔍)
GCVE (CVE): GCVE-0-2023-27650
GCVE (VulDB): GCVE-100-225411
EUVD: 🔍
Entry
Created: 04/10/2023 19:58Updated: 11/19/2025 22:18
Changes: 04/10/2023 19:58 (36), 02/11/2025 17:21 (25), 11/19/2025 22:18 (1)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.