| CVE |
Vendors |
Products |
Updated |
CVSS v3.1 |
| 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. node-tar aims to guarantee that any file whose location would be modified by a symbolic link is not extracted. This is, in part, achieved by ensuring that extracted directories are not symlinks. Additionally, in order to prevent unnecessary stat calls to determine whether a given path is a directory, paths are cached when directories are created. This logic was insufficient when extracting tar files that contained both a directory and a symlink with names containing unicode values that normalized to the same value. Additionally, on Windows systems, long path portions would resolve to the same file system entities as their 8.3 "short path" counterparts. A specially crafted tar archive could thus include a directory with one form of the path, followed by a symbolic link with a different string that resolves to the same file system entity, followed by a file using the first form. By first creating a directory, and then replacing that directory with a symlink that had a different apparent name that resolved to the same entry in the filesystem, it was thus possible to bypass node-tar symlink checks on directories, essentially allowing an untrusted tar file to symlink into an arbitrary location and subsequently extracting arbitrary files into that location, thus allowing arbitrary file creation and overwrite. These issues were addressed in releases 4.4.18, 5.0.10 and 6.1.9. The v3 branch of node-tar has been deprecated and did not receive patches for these issues. If you are still using a v3 release we recommend you update to a more recent version of node-tar. If this is not possible, a workaround is available in the referenced GHSA-qq89-hq3f-393p. |
| In FreeRDP before 2.4.0 on Windows, wf_cliprdr_server_file_contents_request in client/Windows/wf_cliprdr.c has missing input checks for a FILECONTENTS_RANGE File Contents Request PDU. |
| In FreeRDP before 2.4.0 on Windows, wf_cliprdr_server_file_contents_request in client/Windows/wf_cliprdr.c has missing input checks for a FILECONTENTS_SIZE File Contents Request PDU. |
| Win32k Elevation of Privilege Vulnerability |
| Windows SMB Elevation of Privilege Vulnerability |
| Windows Redirected Drive Buffering System Elevation of Privilege Vulnerability |
| Windows SMB Information Disclosure Vulnerability |
| Windows Print Spooler Spoofing Vulnerability |
| Windows Redirected Drive Buffering SubSystem Driver Information Disclosure Vulnerability |
| Windows DNS Elevation of Privilege Vulnerability |
| Windows WLAN AutoConfig Service Elevation of Privilege Vulnerability |
| Windows Subsystem for Linux Elevation of Privilege Vulnerability |
| Windows WLAN AutoConfig Service Remote Code Execution Vulnerability |
| Windows Event Tracing Elevation of Privilege Vulnerability |
| Windows Common Log File System Driver Elevation of Privilege Vulnerability |
| Windows Installer Information Disclosure Vulnerability |
| Windows Installer Denial of Service Vulnerability |
| Windows SMB Information Disclosure Vulnerability |
| Windows Authenticode Spoofing Vulnerability |
| Windows Desktop Bridge Elevation of Privilege Vulnerability |
