Threat Level: green Handler on Duty: Didier Stevens

SANS ISC: InfoSec Handlers Diary Blog - Internet Storm Center Diary 2007-02-13 InfoSec Handlers Diary Blog


Sign Up for Free!   Forgot Password?
Log In or Sign Up for Free!

Microsoft Black Tuesday patches - February 2007

Published: 2007-02-13
Last Updated: 2007-02-16 23:05:40 UTC
by Swa Frantzen (Version: 6)
0 comment(s)

Overview of the February 2007 Microsoft patches and their status.

# Affected Contra Indications Known Exploits Microsoft rating ISC rating(*)
clients servers
MS07-005 Remote code execution in Step-by-Step Interactive training, replaces MS05-031
Step-by-Step Interactive training

CVE-2006-3448
No known problems

KB 923723
No known exploits Important Important Less Urgent
MS07-006 Privilege elevation in Windows Shell, replaces MS06-045
Explorer

CVE-2007-0211
No known problems

KB 928255
No known exploits
Important Important Less Urgent
MS07-007 Privilege elevation in Windows Image Acquisition
Image Acquisition

CVE-2007-0210
No known problems

KB 927802
No known exploits Important Important Less Urgent
MS07-008 Remote code execution in HTML help Active-X, replaces MS06-046
HTML Help

CVE-2007-0214
No known problems

KB 928843
Exploit expected to become public soon
Critical PATCH NOW
Important
MS07-009 Remote code execution in Microsoft MDAC ActiveX, replaces MS06-014
Workaround through a killbit, if you did not do that already: PATCH NOW
MDAC ActiveX

CVE-2006-5559
No known problems

KB 927779
Public exploits since Oct 24th, 2006 Critical Critical
Important
MS07-010 Remote code execution in Microsoft Malware Protection Engine. This will automatically update.
Microsoft malware protection

CVE-2006-5270
No known problems

KB 932135
No known exploits Critical Critical Critical
MS07-011 Remote code execution in Microsoft OLE dialog
OLE

CVE-2007-0026
No known problems

KB 926436
Exploit publicly available
Important Critical Important
MS07-012 Remote code execution in Microsoft Foundation Class
MFC

CVE-2007-0025
No known problems

KB 924667
No known exploits Important Critical Important
MS07-013 Remote code execution in RichEdit, also affects Mac OS X versions of office.
Office

CVE-2006-1311
Autodesk Inventor issues [forum]

KB 918118
No known exploits Important Critical Important
MS07-014 Multiple vulnerabilities in word leading to remote code execution, replaces MS06-060
Office

CVE-2006-5994
CVE-2006-6456
CVE-2006-6561
CVE-2007-0208
CVE-2007-0209
CVE-2007-0515
No known problems

KB 929434
Actively used and publicly known exploits since Dec 5th, 2006.
Critical PATCH NOW
Important
MS07-015 Multiple vulnerabilities in Office lead to remote code execution, replaces MS06-062
Office

CVE-2006-3877
CVE-2007-0671
No known problems

KB 932554
Actively exploited, exploit known since Feb 2nd, 2007.
Critical PATCH NOW
Important
MS07-016 Multiple vulnerabilities in Internet Explorer leading to remote code execution, replaces MS06-072
MSIE

CVE-2006-4697
CVE-2007-0219
CVE-2007-0217
No known problems

KB 928090
Exploits expected to be released soon
Critical PATCH NOW
Important

We will update issues on this page as they evolve.
We appreciate updates
US based customers can call Microsoft for free patch related support on 1-866-PCSAFETY

(*): 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 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.

--
Swa Frantzen -- NET2S

Keywords: mspatchday
0 comment(s)

Valentine card - be sure not to get more than what you expect

Published: 2007-02-13
Last Updated: 2007-02-14 00:38:16 UTC
by Swa Frantzen (Version: 2)
0 comment(s)
Every opportunity where people send each other cards is one of those times the bad folks out there try to do their thing.

Valentines day is no exception to that rule.

We can all try to educate users not to click on attachments that are unexpected or from unknown senders, but how is that going to meet up in real life against the possibility of a hot date with a secret admirer ?

We can try to tackle the problem with technology that scans incoming messages, removes executable content,  repetitive content (spam), etc. but signature based systems will leak exploits, repetition might not always be there and the first few will be passed on regardless and perhaps worst of all, users are generally willing to go through great lengths to get their price and work around extension based filtering.

We could also try to promote not sending media rich wishes. We can lead by example. Simple text in plain old ASCII will do the trick just as well as a 5 Mbyte powerpoint presentation, flash animation or even HTML email.

Anyway, make sure to have a happy February 14th without catching on of these:

Symantec: Trojan.PPDropper.G

Oh, yes it's likely using a fresh so called 0-day, so it seems we'll have more Office patches in a few months time.

With thanks to Juha-Matti for being the first to pointing it out to us. Thanks for some inspiration Steve.
 
--
Swa Frantzen -- NET2S
Keywords:
0 comment(s)

uTorrent exploit public

Published: 2007-02-13
Last Updated: 2007-02-13 21:53:57 UTC
by Swa Frantzen (Version: 1)
0 comment(s)
uTorrent is -I'm told anyway- a popular bittorrent implementation.

It has a publicly available buffer overflow against it, and hence the vulnerability and publication of a matching exploit might cause significant additional risk to your machines/installed user base.

Corporate IT/security managers might -while at it- make sure they are in a position to knowingly allow tools on company owned machines that are mostly, if not exclusively, used for copyright infringements. I'd highly recommend a chat with your legal department on their view on the matter.

Yes, there are some genuine uses of peer to peer file sharing, but they are perhaps better handled when impossible to avoid by an exception or two in the policies.

--
Swa Frantzen -- NET2S
Keywords:
0 comment(s)

Cisco IOS IPS vunerabilities

Published: 2007-02-13
Last Updated: 2007-02-13 20:41:44 UTC
by Swa Frantzen (Version: 1)
0 comment(s)
Cisco released details on vulnerabilities in IOS based IPS.

The vulnerabilities allow IPS evasion and DoS against the device. An upgrade of the IOS version is recommended.

See the Cisco bulletin for more details:
http://www.cisco.com/warp/public/707/cisco-sa-20070213-iosips.shtml

--
Swa Frantzen -- NET2S
Keywords:
0 comment(s)

Y3K problems ?

Published: 2007-02-13
Last Updated: 2007-02-13 15:31:09 UTC
by Swa Frantzen (Version: 2)
0 comment(s)
I almost had a déjà-vu moment when I read: CVE-2007-0842
So time handling functions in Visual C++ 8.0 can't go beyond Jan 1st 3000, didn't the industry learn almost a decade ago that dates move on and building any arbitrary limit is a bad idea(tm).

To add injury to the insult it's not that it returns something indicating it can't handle a date that far in the future, but just throws up an exception and terminates the application, causing opportunity for causing a DoS.

--
Swa Frantzen -- NET2S.com
Keywords:
0 comment(s)
Diary Archives