GHSA-34H3-8MW4-QW57
Vulnerability from github – Published: 2024-03-29 20:16 – Updated: 2024-03-29 20:16Impact
A random segment of ~1-10kb of Node.js heap memory allocated either side of a known buffer will be leaked into the final executable. This memory could contain sensitive information such as environment variables, secrets files, etc.
Patches
This issue is patched in 18.3.1
Workarounds
No workarounds, please update to a patched version of @electron/packager immediately if impacated.
{
"affected": [
{
"package": {
"ecosystem": "npm",
"name": "@electron/packager"
},
"ranges": [
{
"events": [
{
"introduced": "18.3.0"
},
{
"fixed": "18.3.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"18.3.0"
]
}
],
"aliases": [
"CVE-2024-29900"
],
"database_specific": {
"cwe_ids": [
"CWE-402"
],
"github_reviewed": true,
"github_reviewed_at": "2024-03-29T20:16:22Z",
"nvd_published_at": "2024-03-29T16:15:08Z",
"severity": "HIGH"
},
"details": "### Impact\nA random segment of ~1-10kb of Node.js heap memory allocated either side of a known buffer will be leaked into the final executable. This memory _could_ contain sensitive information such as environment variables, secrets files, etc.\n\n### Patches\nThis issue is patched in 18.3.1\n\n### Workarounds\nNo workarounds, please update to a patched version of `@electron/packager` immediately if impacated.\n",
"id": "GHSA-34h3-8mw4-qw57",
"modified": "2024-03-29T20:16:22Z",
"published": "2024-03-29T20:16:22Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/electron/packager/security/advisories/GHSA-34h3-8mw4-qw57"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-29900"
},
{
"type": "WEB",
"url": "https://github.com/electron/packager/commit/d421d4bd3ced889a4143c5c3ab6d95e3be249eee"
},
{
"type": "PACKAGE",
"url": "https://github.com/electron/packager"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
],
"summary": "@electron/packager\u0027s build process memory potentially leaked into final executable"
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.