Lasse Trolle Borup

**Name of the Vulnerable Software and Affected Versions** Cisco AnyConnect Secure Mobility Client for Windows (affected versions not specified) **Description** The issue is related to multiple vulnerabilities in the install, uninstall, and upgrade processes of the software. These vulnerabilities could allow an authenticated, local attacker to hijack DLL or executable files used by the application, potentially executing arbitrary code on an affected device with SYSTEM privileges. The attacker must have valid credentials on the Windows system to exploit these vulnerabilities. Additionally, the vulnerability is associated with the creation of temporary files with insecure permissions during the uninstallation process. **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** Palo Alto Networks Traps versions 5.0 through 5.0.7 Palo Alto Networks Traps versions 6.1 through 6.1.3 **Description** The issue is related to insecure temporary file management, allowing a local authenticated Windows user to escalate privileges or overwrite system files. **Recommendations** For versions 5.0 through 5.0.7, update to version 5.0.8 or later. For versions 6.1 through 6.1.3, update to version 6.1.4 or later.

**Name of the Vulnerable Software and Affected Versions** macOS versions prior to 10.15.4 **Description** A logic issue was addressed with improved state management, allowing a local user to potentially read arbitrary files. **Recommendations** For versions prior to 10.15.4, update to macOS Catalina 10.15.4 to resolve the issue.

**Name of the Vulnerable Software and Affected Versions** Microsoft .NET Framework versions 2.0 through 4.7.2 **Description** An elevation of privilege issue exists that could allow an attacker to elevate their privilege level. To exploit this, an attacker would first have to access the local machine. **Recommendations** For Microsoft .NET Framework versions 2.0 through 4.7.2, at the moment, there is no information about a newer version that contains a fix for this vulnerability.