This two-day concern to the security personnel will pay special attention to these two new disclosure Vulnerability: CVE-2 0 1 4-4 1 1 4 and CVE-2 0 1 4-3 5 6 6 The. Here we have for these two vulnerabilities most some brief description.
CVE-2 0 1 4-4 1 1 4
This vulnerability has this week released the MS14-0 6 0 update in to be repaired, we recommend that users deploy as soon as possible to install this security update to prevent the associated potential threats. This vulnerability exists in Windows System for OLE embedded object processing the way, therefore, although it is anoperating systemthe level of vulnerability, but the most common carrier is Office documents etc support the OLE object file. As mitigation measures, and security best practice, we recommend that all users in the open any unknown origin of the documents should pay special attention, try not to directly open by a stranger to send or share Office, PDF and other documents. About the vulnerability of the more technical analysis of the content, we can refer to<http://www.freebuf.com/news/46956.html> is.
CVE-2 0 1 4-3 5 6 6
In this vulnerability was initially exposed, a lot of people it is, and the recent OpenSSL heart bleed（Heartbleed）vulnerabilities on a par, that its dangers comparable to Heartbleed. But the fact is not the case. Currently CVE-2 0 1 4-3 5 6 6 The main hazards is leakage of the user in the SSL-encrypted channel in information, such as cookies and the like, but the attacker to achieve this attack first in the user's network environment is able to intercept the communication between client and server, and secondly the attacker needs to send a large request to get a cookie the complete contents of the theory is to send 2 5 6 times the request can obtain a byte of information, so attack the implementation of the efficiency is not too good. About the vulnerability of the technical analysis can refer to the <http://drops.wooyun.org/papers/3194> is.
This is a dedicated for SSL 3.0 information disclosure vulnerability, the TLS is not affected. Because SSL 3.0 is an industry security protocols, so it not only affects the Microsoft Windows system, but also equally affects all support for SSL 3.0 with other systems and applications. It is also because this is an industry standard Protocol in the security bug, fix it up was not so easy, Microsoft is currently unable to directly release an update to change the SSL 3.0 Protocol. For the SSL 3.0 Protocol also requires many manufacturers and standards organizations to participate together, to make the most appropriate decision. Microsoft currently has no plans to fully in Windows To disable SSL 3.0, the reason is now there are a very large number of server does not support TLS and only supports SSL, thus fully disabling SSL 3.0 is bound to cause a lot of compatibility issues. For ordinary users, we will disable SSL 3.0 as for the vulnerability of the mitigation measures. In the Disable SSL 3.0 after Of course, the client no longer worry about because of this vulnerability and lead to leakage of information, but if you find that some HTTPS sites cannot be accessed, that is probably because the site only supports SSL. Specific in Windows or IE to disable SSL 3.0 mode please refer to Microsoft's security Advisory 3 0 0 9 0 0 8.