Nelson William Gamazo Sanchez

**Name of the Vulnerable Software and Affected Versions** WSL version 2.5.10 **Description** Microsoft addressed a critical security flaw in Windows Subsystem for Linux (WSL). Details about the issue were initially withheld but are scheduled for release on August 12. **Recommendations** Update to version 2.5.10.

**Name of the Vulnerable Software and Affected Versions** Microsoft Visual Studio (affected versions not specified) **Description** The issue is related to the improper neutralization of special elements used in a command, also known as 'command injection', in Microsoft Visual Studio. This allows an authorized attacker to execute code over a network. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** systemd versions 223 through 235 **Description** The issue allows a remote DNS server to respond with a custom crafted DNS NSEC resource record, triggering an infinite loop in the `dns packet read type window()` function of the 'systemd-resolved' service. This can cause a denial of service (DoS) of the affected service. **Recommendations** For versions 223 through 235, as a temporary workaround, consider disabling the `dns packet read type window()` function until a patch is available. At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** Microsoft Windows versions 8.1, 10 (Gold, 1511, 1607, 1703), Windows Server 2012 R2, Windows Server 2016, and Windows RT 8.1 **Description** The issue is related to a remote code execution vulnerability in the Microsoft Windows Domain Name System (DNS) DNSAPI.dll. It occurs when the system fails to properly handle DNS responses. This can be exploited by a remote attacker using specially crafted DNS responses, potentially allowing them to execute arbitrary code or cause a denial of service. The estimated number of potentially affected devices and details about real-world incidents are not provided. **Recommendations** For Microsoft Windows versions 8.1, 10 (Gold, 1511, 1607, 1703), Windows Server 2012 R2, Windows Server 2016, and Windows RT 8.1, at the moment, there is no information about a newer version that contains a fix for this vulnerability.