Vulnerabilites that are widely known and/or actively exploited are of great interest to our readers, here we try to keep an overview of them
| Affected |
Known Exploits |
Impact |
Known since
|
ISC rating(*) |
| clients |
servers |
Office 2004 vulnerabilities (Mac version)
Unspecified vulnerabilites fixed in a accidentally released patch.
|
Patch has been withdrawn after being exposed to the public and replaced by a patch without the security fixes.
MSRC blog #1
MSRC blog #2
|
unknown
|
Dec 12th, 2006
|
unknown
|
unknown
|
Word unspecified vulnerability #3
CVE-2006-6561
|
Publicly available exploit.
MSRC blog
|
Remote code execution
|
Dec 12th, 2006
|
Critical
|
Important
|
Word unspecified vulnerability #2
CVE-2006-6456
|
MSRC blog #1
MSRC blog #2
Used in targeted attacks
|
Remote code execution
|
Dec 10th, 2006
|
Critical |
Important
|
Word unspecified vulnerability #1
CVE-2006-5994
|
Microsoft Security Advisory 929433
MSRC blog
Used in targeted attacks
|
Remote code execution |
Dec 5th, 2006
|
Critical |
Important
|
RPC in Windows 2004 SP4 UPnP and SPOOLS
CVE-2006-6296
CVE-2006-3644
|
Multiple publicly available exploits.
|
DoS
|
Nov 16th, 2006
|
Less Urgent
|
Important
|
ADODB.Connection ActiveX
CVE-2006-5559
|
MSRC blog
Publicly available exploit.
|
DoS
|
Oct 24th, 2006
|
Less Urgent
|
Less Urgent
|
Microsoft Windows NAT Helper Components
CVE-2006-5614
|
Publicly available exploit.
|
DoS
|
Oct 20th, 2006
|
Less Urgent
|
Important
|
PowerPoint 2003
CVE-2006-5296
|
MSRC blog #1
MSRC blog #2
Publicly available exploit.
|
DoS
|
Oct 20th, 2006
|
Less Urgent
|
Less Urgent
|
Server Service memory corruption
|
Publicly available exploit.
|
Remote code execution?
|
Jul 19th, 2006
|
unknown |
unkown |
(*): ISC rating
- 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 leaisure 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-caserole.
- 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.
--
Swa Frantzen -- Section 66 |
Swa
760 Posts |
