thorfinn: <user name="seedy_girl"> and <user name="thorfinn"> (Default)
[personal profile] thorfinn

Microsoft .NET Remote Code Execution exploit



Similar class of problem as last time with the TCP/IP thing:

From: http://www.auscert.org.au/render.html?it=11798&template=1

===========================================================================
             AUSCERT External Security Bulletin Redistribution

                              ESB-2009.1410.2
           Vulnerabilities in the Microsoft .NET Common Language
                 Runtime Could Allow Remote Code Execution
                              15 October 2009

===========================================================================

        AusCERT Security Bulletin Summary
        ---------------------------------

Product:           Microsoft .NET Framework
                   Microsoft Silverlight
Publisher:         Microsoft
Operating System:  Windows 2000
                   Windows XP
                   Windows Server 2003
                   Windows Vista
                   Windows Server 2008
                   Windows 7
Impact/Access:     Execute Arbitrary Code/Commands -- Remote/Unauthenticated
Resolution:        Patch/Upgrade
CVE Names:         CVE-2009-2497 CVE-2009-0091 CVE-2009-0090

Original Bulletin: 
   http://www.microsoft.com/technet/security/bulletin/ms09-061.mspx


That list of Operating System: entries? That's every single supported version of Windows, from XP (which should be end-of-life but isn't), to Windows 7 (the supposedly new "much more secure" shiny thing). They forgot to put Mac OS in the list - if you have Silverlight installed on a Mac somehow (I don't know who uses it), then it's vulnerable too.

Seriously, if you are a normal person, or even a small business with no ability to pay serious tech-support (and I'm talking about a real network and systems administrator, worth at absolute minimum AUD90k p/a, or a regular contractor worth at least AUD90 per hour for at least a day every week) to make sure you're safe and securely firewalled and patched 100% of the time, don't run Windows, and don't run any Microsoft products if you can help it.

Unless, of course, you don't value about your personal information, anyone else's personal information you might have, your bandwidth, your sales data, your netbanking, and anything else that you might use your computer to access. No worries, have fun with that.




Microsoft Danger Sidekick: All your data are belong to bitbucket



For more fun in that space, late last week, Microsoft managed to blow away all the storage for all Sidekick mobile customers. As in, boom, gone, no backups, kiss all your contacts and anything else supposedly securely backed on their "cloud service" goodbye, unless you were sensible and had your own offline backup (which isn't an officially supported thing on that platform).

See:
T-Mobile Sidekick Disaster: Danger’s Servers Crashed, And They Don’t Have A Backup. There's a rumour today that
Microsoft May Be Able To Restore All Of The Lost Sidekick Data, After All, but so far it's a rumour.

Even if they manage to recover some of the lost data, that's going to be due to heroic manual data recovery of the SAN disks, rather than routine backup restoration. And when I say "routine", I mean - everyone involved in Systems Administration at any serious level knows full well that you have to have a full backup of all data with a regularly tested and validated restore process before you commence any kind of important upgrade.

That is industry standard procedure, and has been industry standard procedure for many decades. Which Microsoft Danger obviously wasn't following. Of course you can play the "blame the subsidiary" card - but they've been a M$ owned company for long enough, with a high profile M$ exec moved in to be in charge for long enough, that basic disaster recovery processes should be in place. There isn't any valid excuse for that kind of data loss by a corporation. None.

ETA: Looks like there has been successful data recovery. Microsoft Confirms Data Recovery for Sidekick Users.

Re: Snow Leopard issue

Date: 2009-10-15 22:24 (UTC)
From: [identity profile] drwally.livejournal.com
Okay big fella, but while you happily lay the boot into MS you were noticeably silent on this one, which smells a little like bias.

DID WINDOWS TOUCH YOU IN THE SWIMSUIT AREA?

Re: Snow Leopard issue

Date: 2009-10-15 23:00 (UTC)
kowari: (Default)
From: [personal profile] kowari
Probably :P but knowing thorf, he probably liked it.

But I get his point of scale. One you can fix with backups and a workaround the other... erm... yeah... oops bye bye secure data.

And the other issue is how many people have .net installed? Farkin' everyone with a windows box which is a LARGE section of the marketplace.

Microsoft still suffers from "people like fucking with MS products" so any tiny hole in their products gets clawed at until it is a gigantic gaping issue. Apple simply doesnt have that culture or marketshare.

*shrug*

I still advocate horses for courses, and there is a good reason I do all my secure internet transactions on my mactop as much as possible and not on my desktop PC or work PC.

Re: Snow Leopard issue

Date: 2009-10-16 00:38 (UTC)
From: [identity profile] drwally.livejournal.com
Is this the kind of thing you're talking about?

http://www.securityfocus.com/bid/10356/discussion/

http://www.informationweek.com/news/hardware/mac/showArticle.jhtml?articleID=216401181

http://www.symantec.com/business/security_response/attacksignatures/detail.jsp?asid=21139

Re: Snow Leopard issue

Date: 2009-10-16 02:14 (UTC)
From: [identity profile] drwally.livejournal.com
Assuming everyone has the latest OS is a bit of a stretch - or that everyone has time machine or an external drive.

However, while it is fair enough to inform everyone of the gaping arseholes of Windows, you do seem to relish the job.

Re: Snow Leopard issue

Date: 2009-10-16 02:48 (UTC)
From: [identity profile] drwally.livejournal.com
My goodness man, how can you expect MS to fix bugs when they are busy making a new Zune?

It's going to RULE THE WORLD

Re: Snow Leopard issue

Date: 2009-10-16 02:47 (UTC)
From: (Anonymous)
It's even rarer than most people think. It requires that one have enabled guest user access in OS X 10.5 and then upgraded to OS X 10.6 and then used guest access again.

-whitebird/Marshall

Re: Snow Leopard issue

Date: 2009-10-16 04:30 (UTC)
tyggerjai: (Default)
From: [personal profile] tyggerjai
Not only - AFAIK it also requires that the guest session was "forcefully terminated" (i.e. hard reboot/crash), and the next login was with the admin account. If you terminate the guest session by logging out, no problem. If you have a hard reboot and then login as guest, or a non-admin account, also no problem, I gather.

April 2015

S M T W T F S
   1234
567891011
12131415 161718
19202122232425
2627282930  

Most Popular Tags

Style Credit

Expand Cut Tags

No cut tags