SABnzbd is an open source binary newsreader. A vulnerability was discovered in SABnzbd that could trick the `filesystem.renamer()` function into writing downloaded files outside the configured Download Folder via malicious PAR2 files. A patch was released as part of SABnzbd 3.2.1RC1. As a workaround, limit downloads to NZBs without PAR2 files, deny write permissions to the SABnzbd process outside areas it must access to perform its job, or update to a fixed version.

Relative path traversal in Microsoft Defender for Endpoint allows an authorized attacker to perform spoofing locally.

Microsoft Exchange Server Remote Code Execution Vulnerability

Relative path traversal in Windows Kerberos allows an authorized attacker to elevate privileges over a network.

Office for Android Spoofing Vulnerability

Windows Hyper-V Remote Code Execution Vulnerability

Windows Remote Desktop Licensing Service Information Disclosure Vulnerability

Relative path traversal in Remote Desktop Client allows an unauthorized attacker to execute code over a network.

Relative path traversal in Remote Desktop Client allows an unauthorized attacker to execute code over a network.

AnySupport (Remote support solution) before 2019.3.21.0 allows directory traversing because of swprintf function to copy file from a management PC to a client PC. This can be lead to arbitrary file execution.

Microsoft Defender for IoT Elevation of Privilege Vulnerability

Windows Kernel Elevation of Privilege Vulnerability

Visual Studio Code Spoofing Vulnerability

NVIDIA Triton Inference Server for Linux and Windows contains a vulnerability where, when it is launched with the non-default command line option --model-control explicit, an attacker may use the model load API to cause a relative path traversal. A successful exploit of this vulnerability may lead to code execution, denial of service, escalation of privileges, information disclosure, and data tampering.

Microsoft SharePoint Information Disclosure Vulnerability

In Splunk Enterprise for Windows versions below 9.3.1, 9.2.3, and 9.1.6, a low-privileged user that does not hold the "admin" or "power" Splunk roles could write a file to the Windows system root directory, which has a default location in the Windows System32 folder, when Splunk Enterprise for Windows is installed on a separate drive.