pkg is tool design to bundle Node.js projects into an executables. Any native code packages built by `pkg` are written to a hardcoded directory. On unix systems, this is `/tmp/pkg/*` which is a shared directory for all users on the same local system. There is no uniqueness to the package names within this directory, they are predictable. An attacker who has access to the same local system has the ability to replace the genuine executables in the shared directory with malicious executables of the same name. A user may then run the malicious executable without realising it has been modified. This package is deprecated. Therefore, there will not be a patch provided for this vulnerability. To check if your executable build by pkg depends on native code and is vulnerable, run the executable and check if `/tmp/pkg/` was created. Users should transition to actively maintained alternatives. We would recommend investigating Node.js 21’s support for single executable applications. Given the decision to deprecate the pkg package, there are no official workarounds or remediations provided by our team. Users should prioritize migrating to other packages that offer similar functionality with enhanced security.
History

No history.

cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published: 2024-02-09T22:21:04.933Z

Updated: 2024-08-22T13:25:19.053Z

Reserved: 2024-01-31T16:28:17.946Z

Link: CVE-2024-24828

cve-icon Vulnrichment

Updated: 2024-08-01T23:28:12.933Z

cve-icon NVD

Status : Analyzed

Published: 2024-02-09T23:15:09.837

Modified: 2024-02-16T13:43:33.407

Link: CVE-2024-24828

cve-icon Redhat

Severity : Moderate

Publid Date: 2024-02-10T00:00:00Z

Links: CVE-2024-24828 - Bugzilla