CVE-2023-39956 json
Electron: Out-of-package code execution when launched with arbitrary cwd
published 3y ago modified 2mo ago also EUVD-2023-2462 , GHSA-7x97-j373-85x5
- cvss
- 6.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 42%
- public exploits
- 0
- none known
Summary
Electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS. Electron apps that are launched as command line executables are impacted. Specifically this issue can only be exploited if the following conditions are met: 1. The app is launched with an attacker-controlled working directory and 2. The attacker has the ability to write files to that working directory. This makes the risk quite low, in fact normally issues of this kind are considered outside of our threat model as similar to Chromium we exclude Physically Local Attacks but given the ability for this issue to bypass certain protections like ASAR Integrity it is being treated with higher importance. This issue has been fixed in versions:`26.0.0-beta.13`, `25.4.1`, `24.7.1`, `23.3.13`, and `22.3.19`. There are no app side workarounds, users must update to a patched version of Electron.
Patch / fix
- npm electron 22.3.19, 23.3.13, 24.7.1, 25.5.0, 26.0.0-beta.13
- electronjs electron 22.3.9, 23.3.13, 24.7.1, 25.5.0
Is CVE-2023-39956 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2y ago
Exploit prediction
0.49% chance of exploitation in the next 30 days, higher than 42% of all scored CVEs (FIRST EPSS, 2026-11-15).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.1 | CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:H/A:L |
| GitHub | 3.1 | 6.1 | CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:H/A:L |
| NVD | 3.1 | 6.6 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:L |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | electron | <22.3.19 >=23.0.0-alpha.1, <23.3.13 >=24.0.0-alpha.1, <24.7.1 >=25.0.0-alpha.1, <25.5.0 >=26.0.0-alpha.1, <26.0.0-beta.13 |
22.3.19 23.3.13 24.7.1 25.5.0 26.0.0-beta.13 |
Affected products
- electron electron
Classification
- Weakness
-
- CWE-94 Improper Control of Generation of Code
References
-
github.com
/electron/electron/security/advisories/GHSA-7x97-j373-85x5
web, vendor-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2023-39956
advisory
-
github.com
/electron/electron
package
Sources
- CVE List CVE-2023-39956
- GitHub Advisory GHSA-7x97-j373-85x5
- NVD CVE-2023-39956
- Maintainer advisory GHSA-7x97-j373-85x5
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of electron/electron published their own advisory on GitHub. Reviewed sources take precedence over it.