Microsoft Announces Special Patch for IE 0-day (Win XP included!)
Microsoft will release a special update later today (10am PT, 1pm ET, 7pm UTC) fixing the Internet Explorer vulnerability which has been used in targeted attacks recently. The vulnerability was announced late last week and affects Internet Explorer 6 and later on Windows versions back to Windows XP. The patch will be published as MS14-021 in line with the May update which is still expected for Tuesday, May 13th.
We do rate this bulletin as "PATCH NOW!" for clients. Even though many organizations started to move away from Internet Explorer as a primary browser, it may still launch in some cases and unless you are using a non-Microsoft operating system you are likely vulnerable. Even servers should apply this patch, but it is less likely that the vulnerability is exposed on a server. Microsoft downplays the risk of the vulnerability for servers by labeling it as "Moderate" due to the crippled default configuration of Internet Explorer on servers.
The patch pre-announcement does specifically list Widnows XP SP3 as vulnerable, indicating that the patch may cover Windows XP SP 3 even though no more patches were expected for Windows XP.
Overview of the May 2014 Microsoft patches and their status.
| # | Affected | Contra Indications - KB | Known Exploits | Microsoft rating(**) | ISC rating(*) | |
|---|---|---|---|---|---|---|
| clients | servers | |||||
| MS14-021 | Vulnerabilities in Internet Explorer | |||||
| Microsoft Internet Explorer CVE-2014-1776 |
KB 2963983 | Used in targeted exploits. | Severity:Critical Exploitability: 1 |
PATCH NOW! | Critical | |
We appreciate updates
US based customers can call Microsoft for free patch related support on 1-866-PCSAFETY
- We use 4 levels:
- PATCH NOW: Typically used where we see immediate danger of exploitation. Typical environments will want to deploy these patches ASAP. Workarounds are typically not accepted by users or are not possible. This rating is often used when typical deployments make it vulnerable and exploits are being used or easy to obtain or make.
- Critical: Anything that needs little to become "interesting" for the dark side. Best approach is to test and deploy ASAP. Workarounds can give more time to test.
- Important: Things where more testing and other measures can help.
- Less Urgent: Typically we expect the impact if left unpatched to be not that big a deal in the short term. Do not forget them however.
- The difference between the client and server rating is based on how you use the affected machine. We take into account the typical client and server deployment in the usage of the machine and the common measures people typically have in place already. Measures we presume are simple best practices for servers such as not using outlook, MSIE, word etc. to do traditional office or leisure work.
- The rating is not a risk analysis as such. It is a rating of importance of the vulnerability and the perceived or even predicted threat for affected systems. The rating does not account for the number of affected systems there are. It is for an affected system in a typical worst-case role.
- Only the organization itself is in a position to do a full risk analysis involving the presence (or lack of) affected systems, the actually implemented measures, the impact on their operation and the value of the assets involved.
- All patches released by a vendor are important enough to have a close look if you use the affected systems. There is little incentive for vendors to publicize patches that do not have some form of risk to them.
(**): The exploitability rating we show is the worst of them all due to the too large number of ratings Microsoft assigns to some of the patches.
[1] https://technet.microsoft.com/en-us/library/security/ms14-may.aspx
------
Johannes B. Ullrich, Ph.D.
SANS Technology Institute
Twitter
| Application Security: Securing Web Apps, APIs, and Microservices | Online | US Eastern | Jan 27th - Feb 1st 2025 |
Comments
Anonymous
May 1st 2014
1 decade ago
Anonymous
May 1st 2014
1 decade ago
-SAM
Anonymous
May 1st 2014
1 decade ago
G
Anonymous
May 2nd 2014
1 decade ago
patermann
Anonymous
May 2nd 2014
1 decade ago
-SAM[/quote]
Nothing new of the wobble of MS SAM. However, like you, I am pleased they did this for the XP users for this reason only. MS has known for years about this issue, long before Vista, 7, 8 et all. One of the many reasons few (like myself) use I.E. Contemporaneously speaking, sad that the GOV did not hold MS accountable for this security issue long ago. Like Java folly, it takes the GOV to say stop using it before companies "smell the coffee" Now the GOV should tack on fee's to these companies when the use lethargic mode in fixing.
Regards..
Anonymous
May 2nd 2014
1 decade ago
Anonymous
May 2nd 2014
1 decade ago