![⚡ THN Weekly Recap: Top Cybersecurity Threats, Tools and Tips [30 Dec]](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgfYK_dlQo9n6UQiuexPS4b1dZ039bN14TXB6AswBkkoRAzzAJg7N3ihBHLhefti8RGcxX6HNI0wVhF8dHLT29WcL2UIUv2n81OsQEbYGKSV6N4aJR-OaK9cV0rWfJWElVsPsjjWvNfb0ZfkRgYfXWIbDBj14YS5VvaBSf7ke5iqzAL2DF7C3IGZRMMwdaf/s1600/recap.png?#)
CVE-2024-53866 - PNPM Package Manager Arbitrary Code Execution Vulnerability
CVE ID : CVE-2024-53866 Published : Dec. 10, 2024, 6:15 p.m. | 1 hour, 44 minutes ago Description : The package manager pnpm prior to version 9.15.0 seems to mishandle overrides and global cache: Overrides from one workspace leak into npm metadata saved in global cache; npm metadata from global cache affects other workspaces; and installs by default don't revalidate the data (including on first lockfile generation). This can make workspace A (even running with `ignore-scripts=true`) posion global cache and execute scripts in workspace B. Users generally expect `ignore-scripts` to be sufficient to prevent immediate code execution on install (e.g. when the tree is just repacked/bundled without executing it). Here, that expectation is broken. Global state integrity is lost via operations that one would expect to be secure, enabling subsequently running arbitrary code execution on installs. Version 9.15.0 fixes the issue. As a work-around, use separate cache and store dirs in each workspace. Severity: 0.0 | NA Visit the link for more details, such as CVSS details, affected products, timeline, and more...
CVE ID : CVE-2024-53866
Published : Dec. 10, 2024, 6:15 p.m. | 1 hour, 44 minutes ago
Description : The package manager pnpm prior to version 9.15.0 seems to mishandle overrides and global cache: Overrides from one workspace leak into npm metadata saved in global cache; npm metadata from global cache affects other workspaces; and installs by default don't revalidate the data (including on first lockfile generation). This can make workspace A (even running with `ignore-scripts=true`) posion global cache and execute scripts in workspace B. Users generally expect `ignore-scripts` to be sufficient to prevent immediate code execution on install (e.g. when the tree is just repacked/bundled without executing it). Here, that expectation is broken. Global state integrity is lost via operations that one would expect to be secure, enabling subsequently running arbitrary code execution on installs. Version 9.15.0 fixes the issue. As a work-around, use separate cache and store dirs in each workspace.
Severity: 0.0 | NA
Visit the link for more details, such as CVSS details, affected products, timeline, and more...
Published : Dec. 10, 2024, 6:15 p.m. | 1 hour, 44 minutes ago
Description : The package manager pnpm prior to version 9.15.0 seems to mishandle overrides and global cache: Overrides from one workspace leak into npm metadata saved in global cache; npm metadata from global cache affects other workspaces; and installs by default don't revalidate the data (including on first lockfile generation). This can make workspace A (even running with `ignore-scripts=true`) posion global cache and execute scripts in workspace B. Users generally expect `ignore-scripts` to be sufficient to prevent immediate code execution on install (e.g. when the tree is just repacked/bundled without executing it). Here, that expectation is broken. Global state integrity is lost via operations that one would expect to be secure, enabling subsequently running arbitrary code execution on installs. Version 9.15.0 fixes the issue. As a work-around, use separate cache and store dirs in each workspace.
Severity: 0.0 | NA
Visit the link for more details, such as CVSS details, affected products, timeline, and more...
