![]() ![]() Private or Domain) the vulnerability can be reached by remote, unauthenticated users.įor an attacker to be able to trigger the vulnerability on a target, they need to know the WSD Address value for the target, which is a UUID (Universally Unique Identifier). This means under non-Public profiles (e.g. The Windows Firewall will allow messages in to these ports if the interface firewall profile is anything other than Public. Whether a system has WSD ports active and listening depends on the system configuration and applications that are installed.īy default, WSDAPI will listen on TCP ports 53. Only systems with the WSD TCP ports active and listening are vulnerable to the most likely attack vector. WSDAPI was introduced in Windows Vista and hence earlier versions of Windows are not vulnerable. Windows Vista and Windows Server 2008 are affected. To be clear, the vulnerability is in the Windows module used to interact with devices that support Web Services on Devices, and does not affect the devices themselves. ![]() This can cause the service or application to crash, or could lead to Remote Code Execution. We will describe the vulnerability and mitigating factors in more detail in this blog post.Ī long header value within a WSD message can lead to stack corruption within the process hosting WSDApi.dll. There are mitigating factors that limit the scenarios where the vulnerability can be exploited.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |