Electron up to 28.3.1/29.3.2/30.0.2 heap-based overflow
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.3 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in Electron up to 28.3.1/29.3.2/30.0.2. This impacts the function nativeImage.createFromPath/nativeImage.createFromBuffer. The manipulation leads to heap-based overflow.
This vulnerability is uniquely identified as CVE-2024-46993. Local access is required to approach this attack. No exploit exists.
You should upgrade the affected component.
Details
A vulnerability was found in Electron up to 28.3.1/29.3.2/30.0.2. It has been rated as critical. This issue affects the function nativeImage.createFromPath/nativeImage.createFromBuffer. The manipulation with an unknown input leads to a heap-based overflow vulnerability. Using CWE to declare the problem leads to CWE-122. A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc(). Impacted is confidentiality, integrity, and availability. The summary by CVE is:
Electron is an open source framework for writing cross-platform desktop applications using JavaScript, HTML and CSS. In versions prior to 28.3.2, 29.3.3, and 30.0.3, the nativeImage.createFromPath() and nativeImage.createFromBuffer() functions call a function downstream that is vulnerable to a heap buffer overflow. An Electron program that uses either of the affected functions is vulnerable to a buffer overflow if an attacker is in control of the image's height, width, and contents. This issue has been patched in versions 28.3.2, 29.3.3, and 30.0.3. There are no workarounds for this issue.
The advisory is shared at github.com. The identification of this vulnerability is CVE-2024-46993 since 09/16/2024. The exploitation is known to be difficult. An attack has to be approached locally. Technical details are known, but no exploit is available.
Upgrading to version 28.3.2, 29.3.3 or 30.0.3 eliminates this vulnerability.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 4.5VulDB Meta Temp Score: 4.3
VulDB Base Score: 4.5
VulDB Temp Score: 4.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
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: Heap-based overflowCWE: CWE-122 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
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: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Electron 28.3.2/29.3.3/30.0.3
Timeline
09/16/2024 CVE reserved07/01/2025 Advisory disclosed
07/01/2025 VulDB entry created
07/01/2025 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-6r2x-8pq8-9489
Status: Confirmed
CVE: CVE-2024-46993 (🔒)
GCVE (CVE): GCVE-0-2024-46993
GCVE (VulDB): GCVE-100-314477
Entry
Created: 07/01/2025 06:57Updated: 07/01/2025 14:27
Changes: 07/01/2025 06:57 (68), 07/01/2025 11:07 (1), 07/01/2025 14:27 (1)
Complete: 🔍
Cache ID: 216::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.