Notion up to 3.1.0 on macOS RunAsNode/enableNodeClilnspectArguments privilege escalation

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.
4.2$0-$5k0.00

Summaryinfo

A vulnerability marked as critical has been reported in Notion up to 3.1.0 on macOS. This affects an unknown function. Performing a manipulation of the argument RunAsNode/enableNodeClilnspectArguments results in an unknown weakness. This vulnerability is cataloged as CVE-2024-23743. It is possible to initiate the attack remotely. There is no exploit available.

Detailsinfo

A vulnerability was found in Notion up to 3.1.0 on macOS. It has been classified as critical. The manipulation of the argument RunAsNode/enableNodeClilnspectArguments 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 in Notion for macOS version 3.1.0 and before, allows remote attackers to execute arbitrary code via the RunAsNode and enableNodeClilnspectArguments components.

The weakness was shared 01/28/2024. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2024-23743 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.

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

Productinfo

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 4.3
VulDB Meta Temp Score: 4.2

VulDB Base Score: 6.3
VulDB Temp Score: 6.1
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 3.3
NVD Vector: 🔍

CNA Base Score: 3.3
CNA Vector: 🔍

CVSSv2info

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

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

Exploitinginfo

Class: Privilege escalation
CWE: Unknown
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: Yes

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

01/21/2024 🔍
01/28/2024 +7 days 🔍
01/28/2024 +0 days 🔍
09/26/2024 +241 days 🔍

Sourcesinfo

Advisory: github.com
Status: Not defined

CVE: CVE-2024-23743 (🔍)
GCVE (CVE): GCVE-0-2024-23743
GCVE (VulDB): GCVE-100-252249

Entryinfo

Created: 01/28/2024 09:49
Updated: 09/26/2024 01:42
Changes: 01/28/2024 09:49 (36), 02/21/2024 08:11 (11), 08/02/2024 12:36 (15), 09/26/2024 01:42 (11)
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!