CVE-2024-24828: Local Privilege Escalation in execuatables bundled by pkg
Impact 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.
Patches This package is deprecated. Therefore, there will not be a patch provided for this vulnerability.
Recommended Action: 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.
Workarounds 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.
Other sources
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.
— MITRE
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2024-24828?
CVE-2024-24828 is classified as a high severity vulnerability due to potential security risks associated with shared directories.
How do I fix CVE-2024-24828?
To fix CVE-2024-24828, you should upgrade the pkg package to version 5.8.2 or later.
What are the affected versions for CVE-2024-24828?
CVE-2024-24828 affects pkg versions up to and including 5.8.1.
What impact does CVE-2024-24828 have on my system?
CVE-2024-24828 allows for potential interference with package names in a shared directory, risking conflicts and unauthorized access.
Is CVE-2024-24828 present in npm packages?
Yes, CVE-2024-24828 is found in npm pkg packages version 5.8.1 and below.