|

|
User Controls
|
New User
|
Login
|
Edit/View My Profile
|

|

|

|
ActiveMac
|
Articles
|
Forums
|
Links
|
News
|
News Search
|
Reviews
|

|

|

|
News Centers
|
Windows/Microsoft
|
DVD
|
ActiveHardware
|
Xbox
|
MaINTosh
|
News Search
|

|

|

|
ANet Chats
|
The Lobby
|
Special Events Room
|
Developer's Lounge
|
XBox Chat
|

|

|

|
FAQ's
|
Windows 98/98 SE
|
Windows 2000
|
Windows Me
|
Windows "Whistler" XP
|
Windows CE
|
Internet Explorer 6
|
Internet Explorer 5
|
Xbox
|
DirectX
|
DVD's
|

|

|

|
TopTechTips
|
Registry Tips
|
Windows 95/98
|
Windows 2000
|
Internet Explorer 4
|
Internet Explorer 5
|
Windows NT Tips
|
Program Tips
|
Easter Eggs
|
Hardware
|
DVD
|

|

|

|
Latest Reviews
|
Applications
|
Microsoft Windows XP Professional
|
Norton SystemWorks 2002
|

|
Hardware
|
Intel Personal Audio Player
3000
|
Microsoft Wireless IntelliMouse
Explorer
|

|

|

|
Site News/Info
|
About This Site
|
Affiliates
|
ANet Forums
|
Contact Us
|
Default Home Page
|
Link To Us
|
Links
|
Member Pages
|
Site Search
|
Awards
|

|

|

|
Credits
©1997/2004, Active Network. All
Rights Reserved.
Layout & Design by
Designer Dream. Content
written by the Active Network team. Please click
here for full terms of
use and restrictions or read our
Privacy Statement.
|
|
|
 |
|
#1 By
24214 (170.63.96.108)
at
10/23/2008 9:57:08 AM
|
Word on the street is whatever this patches could have implications on levels of Nimda if you don't patch.
|
#2 By
23275 (71.91.9.16)
at
10/23/2008 10:02:25 AM
|
any truth to it being related to a kernel level function of how much memory is allocated within kernel space for unassembled tcp sessions? If so, plan on patching the moment a patch is issued.
This post was edited by lketchum on Thursday, October 23, 2008 at 10:11.
|
#3 By
24214 (170.63.96.108)
at
10/23/2008 10:19:55 AM
|
I don't know the details yet, but we've already made the decision to patch at release w/o testing after speaking with our TAM.
|
#4 By
23275 (71.91.9.16)
at
10/23/2008 11:13:22 AM
|
#3, same here - capturing new ASR's/ERD's and Last Known State across the board now and ahead of release.
The harder part is how best, and without much good information at all, to communicate what we have to do and why, with customers without sounding alarmist - while stressing the importance of near-immediate action.
This post was edited by lketchum on Thursday, October 23, 2008 at 15:04.
|
#5 By
1896 (68.153.171.248)
at
10/23/2008 12:18:53 PM
|
#3: Same here; no matter that for Vista and Server 2008 is rated "Important" and not "Critical", we will install it right away.
Just in case we have imaged everything :-)
I would also say that I am pleased with the way MS acted: quick and responsible.
This post was edited by Fritzly on Thursday, October 23, 2008 at 12:19.
|
#7 By
24214 (170.63.96.108)
at
10/23/2008 2:49:13 PM
|
Just got off of a call with our http://www.msisac.org/ partners and there are reported exploits in the wild already. Client OS version of the exploit requires NO authentication to happen. The sever OS version does by default unless you've customized server default security to a lesser level require Authentication to perform.
|
#8 By
54556 (68.35.10.96)
at
10/24/2008 8:04:00 AM
|
The patch was released on the 12th with all the other Patch Tuesday patches. The only thing that is "out of band" here is the notification update.
The "out of band" exploit is RPC based to the server service, the relevant port should be blocked at a business' firewalls as a matter of best practices anyway, minimizing the vulnerability.
#5, You don't test all patches??? Amazing.
This post was edited by notketchum on Friday, October 24, 2008 at 08:12.
|
#9 By
17855 (205.167.180.132)
at
10/24/2008 8:45:51 AM
|
#8 Where do find that it was released on 10/12/2008? All relevent information on KB958644 indicates it was released 10/22/2008.
|
#10 By
1896 (68.153.171.248)
at
10/24/2008 8:49:47 AM
|
#8: Usually we do; considering the urgency I decided to install it right away.
Granted we are not speaking of a 5000 desktop domain here so I can take shortcuts that bigger companies could not.
Besides my understanding is that yesterday patch is a "revised" one and not the same released on Tuesday, again just my understanding.
This post was edited by Fritzly on Friday, October 24, 2008 at 08:50.
|
#11 By
23275 (71.91.9.16)
at
10/24/2008 8:56:04 AM
|
#9, the OOB update actually updates the netapi32.dll that was first updated 8 Aug, 2006 - that is the vuln. It is accessed via the RPC Server Service and you are right, the revised update was released on the 23rd.
TCP ports 139 and 445, which are normally blocked by enterprises and SOHO NAT devices do mitigate the vuln.; however, XP clients under certain circumstances and regardless of their own firewalls being on, would still be vulnerable.
Since the exploit is potentially wormable, MS assessed the threat to be significant enough to warrant an OOB update - in light of exploit code being discovered in the wild by the MS Fore Front and Live OneCare teams.
Of interest to me was the original concern that the specific area being exploited in netapi32.dll as accessed via the RPC Server Service, did relate to our initial concerns about unassembled tcp sessions. Not hard to conclude when the alert said "all supported operating systems" - so it was probable that an earlier update was the subject of analysis and the only one in recent memory that would also be shared would have been the vuln. originally addressed in Aug 2006.
This post was edited by lketchum on Friday, October 24, 2008 at 08:57.
|
#12 By
23275 (71.91.9.16)
at
10/24/2008 9:11:23 AM
|
REF my 11 above - if you're interested in the original MS06-040 that the OOB updated on the 23rd, here it is, http://www.microsoft.com/technet/security/bulletin/ms06-040.mspx
Additional fixes were released on 12th Sep, 2006 which addressed performance issues induced by the original update as at, KB921883
|
#13 By
2960 (70.177.180.170)
at
10/24/2008 12:56:58 PM
|
It installed on my machine overnight automatically.
TL
|
#14 By
2332 (66.92.78.241)
at
10/24/2008 4:54:55 PM
|
This is a very serious bug. I spent most of the day patching my office and production environments. I'm now 100% patched.
Microsoft would only have done an out-of-band release if they were seeing attack code in the wild. Otherwise it would have waited until November's Patch Tuesday release.
That said, I have a feeling the affects of this will be minimal. Virtually all organizations block the ports needed for this to work. (We certainly do.) So the threat is limited to infected machines being introduced inside the firewall.
Thanks to Windows Update, most user's home machines should be patched be the end of the weekend. Much like a vaccination for the flu, as long as a large percentage of machines are patched, it becomes extremely difficult for infected machines to spread the worm.
I'm sure we'll hear about some corporate network being owned, but overall this won't be another Nimda. Times have changed.
|
|
|
 |
|