CVE-2023-30586
nodejs: OpenSSL engines can be used to bypass the permission model
Overview
Description
A privilege escalation vulnerability exists in Node.js 20 that allowed loading arbitrary OpenSSL engines when the experimental permission model is enabled, which can bypass and/or disable the permission model. The attack complexity is high. However, the crypto.setEngine() API can be used to bypass the permission model when called with a compatible OpenSSL engine. The OpenSSL engine can, for example, disable the permission model in the host process by manipulating the process's stack memory to locate the permission model Permission::enabled_ in the host process's heap memory. Please note that at the time this CVE was issued, the permission model is an experimental feature of Node.js.
Source: OX vulnerability database
Severity
7.5 · HIGH
CVSS 3.1 base score, scored by NVD.
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Weakness: CWE-862
Affected packages · 2
Operating systems · 3 fixes
chainguard 1 release · 1 package
| Release | Package | Fixed in |
|---|---|---|
| nodejs-20 | 20.3.1-r0 |
openSUSE 1 release · 1 package
| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Tumbleweed | corepack20 +4 | 20.3.1-1.1 | openSUSE-SU-2024:13021-1 |
wolfi 1 release · 1 package
| Release | Package | Fixed in |
|---|---|---|
| nodejs-20 | 20.3.1-r0 |
References
- access.redhat.com https://access.redhat.com/security/cve/CVE-2023-30586
- hackerone.com https://hackerone.com/reports/1954535
- nvd.nist.gov https://nvd.nist.gov/vuln/detail/CVE-2023-30586
- security.netapp.com https://security.netapp.com/advisory/ntap-20230803-0008/
- www.cve.org https://www.cve.org/CVERecord?id=CVE-2023-30586
OX Radar and Response Center
Find threats in your stack.
OX Radar can check high-priority threats, like critical package CVEs, against your context.
Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.