Discord up to 0.0.291 on macOS Setting RunAsNode/enableNodeClilnspectArguments privilege escalation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.9 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Discord up to 0.0.291 on macOS. It has been rated as critical. This issue affects some unknown processing of the component Setting Handler. The manipulation of the argument RunAsNode/enableNodeClilnspectArguments leads to an unknown weakness. This vulnerability is referenced as CVE-2024-23739. Remote exploitation of the attack is possible. No exploit is available.
Details
A vulnerability, which was classified as critical, has been found in Discord up to 0.0.291 on macOS. This issue affects an unknown function of the component Setting Handler. The manipulation of the argument RunAsNode/enableNodeClilnspectArguments with an unknown input leads to a unknown weakness. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
An issue in Discord for macOS version 0.0.291 and before, allows remote attackers to execute arbitrary code via the RunAsNode and enableNodeClilnspectArguments settings.
The weakness was published 01/28/2024. The advisory is shared at github.com. The identification of this vulnerability is CVE-2024-23739 since 01/21/2024. 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.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
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
01/21/2024 🔍01/28/2024 🔍
01/28/2024 🔍
05/30/2025 🔍
Sources
Advisory: github.comStatus: Not defined
CVE: CVE-2024-23739 (🔍)
GCVE (CVE): GCVE-0-2024-23739
GCVE (VulDB): GCVE-100-252245
Entry
Created: 01/28/2024 09:48Updated: 05/30/2025 01:27
Changes: 01/28/2024 09:48 (37), 02/21/2024 07:54 (11), 05/30/2025 01:27 (15)
Complete: 🔍
Cache ID: 216:272:103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.