MS15-061 patches eight different software flaws in the kernel, including cve-2015-2360
Microsoft releases eight security bulletins today, updating a set of forty five software vulnerabilities. This month’s updates touch a smaller set of Microsoft software, but two of the Bulletins address kernel-level vulnerabilities and require a restart. Some are being exploited as a part of serious targeted attack activity:
- Windows Kernel, win32k.sys (MS15-061)
- Internet Explorer – critical
- Windows Media Player – critical
- Microsoft Common Controls
- Microsoft Office
- Active Directory Federation Services
- Exchange Server
Two are rated Critical (MS15-056 for Internet Explorer and MS15-057 for Windows Media Player) because of their remote code execution severity. The Internet Explorer bulletin alone fixes over 20 memory corruption vulnerabilities in the IE codebase.
Most interesting of all the bulletins this month turns out to be MS15-061, patching eight different software flaws in the kernel. In particular, cve-2015-2360 was a difficult find, and this 0day was reported by our own talented colleague Maxim Golovkin. This issue presented itself within win32k.sys, which fails to properly free memory after use. It might be rated “Important” as an escalation of privilege vulnerability, but defending against its deployment as a part of targeted attack activity is most certainly critical.
Please update your Windows systems asap.
Microsoft Security Updates June 2015
Pierre Samson
Very informative for a home user. Thank you.
Pierre
frank scandle
good to know there are people who care and give good information.thank you for your expertise.
Jim Waller
The articles contained in “SECURELIST” are quite informative. If possible, as you report future Microsoft Security Issues and patches, please also refer to their “KB” Number which represents the identifier after the product is actually installed. The “MS” Number, example (MS15-061) requires users to take the added step of looking up patch details at Microsoft’s website. As a trace this becomes particularly burdensome for users and system administrators investigating whether the software was actually installed on a client’s machine; especially when some front end users have windows set to automatically download and install software. // Jim Waller, 29Jun2015.