Node.js process.binding permission

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

Summaryinfo

A vulnerability marked as critical has been reported in Node.js. This affects the function process.binding. This manipulation causes permission. This vulnerability is handled as CVE-2023-32559. There is not any exploit available. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability has been found in Node.js (JavaScript Library) (the affected version is unknown) and classified as critical. Affected by this vulnerability is the function process.binding. The manipulation with an unknown input leads to a permission vulnerability. The CWE definition for the vulnerability is CWE-275. As an impact it is known to affect confidentiality, integrity, and availability.

The weakness was released 08/10/2023. The advisory is shared at nodejs.org. This vulnerability is known as CVE-2023-32559 since 05/10/2023. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1222 for this issue.

The vulnerability scanner Nessus provides a plugin with the ID 216256 (Oracle Linux 8 : nodejs:20 (ELSA-2025-1351)), which helps to determine the existence of the flaw in a target environment.

Upgrading eliminates this vulnerability.

The vulnerability is also documented in the databases at Tenable (216256) and EUVD (EUVD-2023-36803). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Name

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.5
VulDB Meta Temp Score: 6.4

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

NVD Base Score: 7.5
NVD Vector: 🔍

CVSSv2info

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

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

Exploitinginfo

Class: Permission
CWE: CWE-275 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 216256
Nessus Name: Oracle Linux 8 : nodejs:20 (ELSA-2025-1351)

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Timelineinfo

05/10/2023 🔍
08/10/2023 +92 days 🔍
08/10/2023 +0 days 🔍
05/08/2026 +1002 days 🔍

Sourcesinfo

Advisory: nodejs.org
Status: Confirmed

CVE: CVE-2023-32559 (🔍)
GCVE (CVE): GCVE-0-2023-32559
GCVE (VulDB): GCVE-100-236821
EUVD: 🔍

Entryinfo

Created: 08/10/2023 18:26
Updated: 05/08/2026 10:52
Changes: 08/10/2023 18:26 (36), 09/05/2023 10:34 (1), 09/05/2023 10:40 (11), 10/03/2024 17:17 (21), 02/14/2025 13:11 (2), 07/02/2025 03:58 (1), 05/08/2026 10:49 (1), 05/08/2026 10:52 (4)
Complete: 🔍
Committer: lywand
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!