12/28/2022 0 Comments Java 1.7.0_79 downloadThere is no reasonable way to work around this issue without performing the same path normalization procedures that node-tar now does. If you are still using a v3 release we recommend you update to a more recent version of node-tar. The v3 branch of node-tar has been deprecated and did not receive patches for these issues. These issues were addressed in releases 4.4.18, 5.0.10 and 6.1.9. This only affects users of `node-tar` on Windows systems. Additionally, a `.` portion of the path could occur immediately after the drive letter, such as `C./foo`, and was not properly sanitized by the logic that checked for `.` within the normalized and split portions of the path. If the drive letter does not match the extraction target, for example `D:\extraction\dir`, then the result of `path.resolve(extractionDirectory, entryPath)` would resolve against the current working directory on the `C:` drive, rather than the extraction target directory. This logic was insufficient on Windows systems when extracting tar files that contained a path that was not an absolute path, but specified a drive letter different from the extraction target, such as `C:some\path`. This is, in part, accomplished by sanitizing absolute paths of entries within the archive, skipping archive entries that contain `.` path portions, and resolving the sanitized paths against the extraction target directory. node-tar aims to guarantee that any file whose location would be outside of the extraction target directory is not extracted. The npm package "tar" (aka node-tar) before versions 4.4.18, 5.0.10, and 6.1.9 has an arbitrary file creation/overwrite and arbitrary code execution vulnerability. This is patched in 2.8.2 which is included in npm v7.20.7 and above. Anyone using npm v7.20.6 or earlier on a case-insensitive filesystem is potentially affected. On case-insensitive file systems, if `pwn-a` was installed, and then `pwn-b` was installed afterwards, the contents of `foo.tgz` would be written to `/some/path`, and any existing contents of `/some/path` would be removed. Another package, `pwn-b` could define a dependency such as `FOO: "file:foo.tgz"`. For example, a package `pwn-a` could define a dependency in their `package.json` file such as `"foo": "file:/some/path"`. Combined with a symlink dependency such as `file:/some/path`, this allowed an attacker to create a situation in which arbitrary contents could be written to any location on the filesystem. However, on case-insensitive file systems (such as macOS and Windows), this is not the case. When multiple dependencies differ only in the case of their name, Arborist's internal data structure saw them as separate items that could coexist within the same level in the `node_modules` hierarchy. This is, in part, accomplished by resolving dependency specifiers defined in `package.json` manifests for dependencies with a specific name, and nesting folders to resolve conflicting dependencies. Sources of the patches are available here.Not the library that calculates dependency trees and manages the `node_modules` folder hierarchy for the npm command line interface, aims to guarantee that package dependency contracts will be met, and the extraction of package contents will always be performed into the expected folder. The light version supports fewer features, but it is still more advanced than the default OpenJDK redefinition functionality, and it is easier to keep in sync with the OpenJDK HotSpot. Thus, it is supported for fewer versions of OpenJDK. The full version supports more features (for example, it supports the removal of superclasses), but it is harder to maintain. Old full version (with parent class modification support):
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |