Shmuel Uzan

The issue is related to improper input validation in Microsoft Office Outlook, allowing an authorized attacker to execute code locally. This can also enable remote attackers to execute arbitrary code and affect the system.

A critical issue in Microsoft Office Outlook allows an authorized attacker to execute code locally. This is due to a path traversal problem. The issue can be exploited by attackers using social engineering to gain low-privilege access. There are reports of this issue being actively exploited.

Name of the Vulnerable Software and Affected Versions: Microsoft Outlook (affected versions not specified) Description: The issue is related to incorrect external control of a file name or path in Microsoft Outlook for Windows operating systems. Exploitation of this issue may allow an attacker to execute arbitrary code. It is described as a Form Injection Remote Code Execution (RCE) vulnerability. Researchers from Morphisec Threat Labs have identified this vulnerability, which is a zero-click vulnerability leveraging form injections. 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: Microsoft Outlook versions prior to the fixed version Description: A critical zero-click remote code execution vulnerability has been discovered in Microsoft Outlook. This vulnerability allows attackers to execute arbitrary code by sending a specially crafted email. The issue is related to the use of an incomplete blacklist when processing input data, which can be exploited by creating specially formed DLL files. The vulnerability can be triggered without any user interaction, simply by opening a malicious email. Recommendations: For Microsoft Outlook versions prior to the fixed version, update to the latest version to resolve the issue. As a temporary workaround, consider disabling the auto-open email feature to minimize the risk of exploitation. Restrict access to vulnerable modules to minimize the risk of exploitation. Avoid using vulnerable parameters in affected API endpoints until the issue is resolved. At the moment, there is no information about a newer version that contains a fix for this vulnerability.