Last Updated: 2011-02-08 23:49:20 UTC
by Adrien de Beaupre (Version: 1)
When is a 0day not a 0day? When the exploit ends up being just a poor default configuration issue. It can lead to files being read, that the user has permission to read. Like /etc/passwd for example. The solution? Set "wide links = no" in the [global] section of your smb.conf and restart smbd to eliminate this problem, from the Samba Symlink Attack posting here. Thanks Elazar!
Adrien de Beaupré
Last Updated: 2010-02-09 19:28:42 UTC
by Johannes Ullrich (Version: 1)
Overview of the February 2010 Microsoft patches and their status.
|#||Affected||Contra Indications||Known Exploits||Microsoft rating||ISC rating(*)|
|MS10-003||Vulnerability in Microsoft Office (MSO) Could Allow Remote Code Execution (Windows and OS X) (Replaces MS09-062)|
|KB 978214||no known exploits.||Severity:Important
|MS10-004||Vulnerabilities in Microsoft Office PowerPoint Could Allow Remote Code Execution (Windows and OS X)|
|KB 975416||no known exploits.||Severity:Critical
|MS10-005||Vulnerability in Microsoft Paint Could Allow Remote Code Execution|
|KB 978706||no known exploits.||Severity:Moderate
|MS10-006||Vulnerabilities in SMB Client Could Allow Remote Code Execution (Replaces MS06-030 MS08-068 )|
|KB 978251||no known exploits.||Severity:Critical
|MS10-007||Vulnerability in Windows Shell Handler Could Allow Remote Code Execution|
|KB 975713||no known exploits.||Severity:Critical
|MS10-008||Cumulative Security Update of ActiveX Kill Bits (Replaces MS09-055)|
|KB 978262||no known exploits.||Severity:Critical
|MS10-009||Vulnerabilities in Windows TCP/IP Could Allow Remote Code Execution|
|KB 974145||no known exploits.||Severity:Critical
|MS10-010||Hyper-V Instruction Set Validation Vulnerability|
|KB 977894||no known exploits.||Severity:Important
|MS10-011||Vulnerability in Windows Client/Server Run-time Subsystem Could Allow Elevation of Privileges|
|KB 978037||no known exploits.||Severity:Important
|MS10-012||Vulnerabiliites in SMB Server Could Allow Remote Code Execution (Replaces MS09-001)|
|KB 971468||no known exploits.||Severity:Important
|MS10-013||Vulnerability in Microsoft DirectShow Could Allow Remote Code Execution MS09-038 (Replaces MS09-038 MS09-028 )|
|KB 977935||no known exploits.||Severity:Critical
|MS10-014||Vulnerability in Kerberos Could Allow Denial of Service|
|KB 977290||no known exploits.||Severity:Important
|MS10-015||Vulnerabilities in Windows Kernel Could Allow Elevation of Privilege|
|KB 977165||exploit available||Severity:Important
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