Good idea mate, now everyone who didnt know before now can. I patched XP as soon as I read the thread sometime last week saying "Download is important by the latest Monday". Scared me
good god that was not cool
thanks for having this thread up today blackhawk... you saved me
0
BlackHawkBible music connoisseurThere's no place like 127.0.0.1Icrontian
edited August 2003
Glad to help although I just wanted to put this help so others didn't have to search. Pic was from fuxor's thread along with the link posted by shorty. I still haven't got the problem.
Patch and then scanner run are recommended, and the OLD scanner for RPC flaws will report system is not patched.
These are not XP only bugs, and two are buffer overflows and one is a flaw that lets an RPC data OVERLOAD yield complete access to a computer and DDOS use of it. I will try to follow through with more inof tomorrow when I get more details, but the Microsft Security advisory is here:
NT based Windows O\Ss ALL are affected, ME and down except for NT 4.0 are NOT capable of having this bug set even if DCOM is installed.
Article is on support and a search of 'RPC Patch' led to Security Advisory MS03-039 which also should relate to Q824146 (note that the formal Q article was NOT posted as of 12:03 AM EDT US time, and support seems to have MANY requests for this advisory now and had to be refreshed twice to get to the Security Advisory). Microsoft is aksing ALL businesses to patch immediately, and ZDNet is expecting viruses and or trojans to become extant quickly so those with XP Pro need to patch also. XP Home is affected and needs to be patched also, but figure most here use Pro. Server 2003 is affected, 2000 Pro and servers also, and NT 4.0-- other than all of XP as operating system which is ALSO affected.
Please be warned here first. Blocking with firewalls can be done if you block RPC inbound and outbound (Microsoft has an article linked to in advisory with port numbers), but the patches probably are to prevent repercussions from doing so also adn all need to take note of this.
Admins may break thread off here if wanted, but please sticky it also unless you wish the thread topic to be handling recent RPC problems for more than one recent vulnerability that is now officially more than 4 (older ones exist also).
John-- who is tagging onto and expanding a thread, and absolutely not trying to hijack it.
Comments
thanks for having this thread up today blackhawk... you saved me
http://zdnet.com.com/2100-1104_2-5074415.html
Patch and then scanner run are recommended, and the OLD scanner for RPC flaws will report system is not patched.
These are not XP only bugs, and two are buffer overflows and one is a flaw that lets an RPC data OVERLOAD yield complete access to a computer and DDOS use of it. I will try to follow through with more inof tomorrow when I get more details, but the Microsft Security advisory is here:
http://support.microsoft.com/default.aspx?scid=kb;en-us;824146
Quick summary:
NT based Windows O\Ss ALL are affected, ME and down except for NT 4.0 are NOT capable of having this bug set even if DCOM is installed.
Article is on support and a search of 'RPC Patch' led to Security Advisory MS03-039 which also should relate to Q824146 (note that the formal Q article was NOT posted as of 12:03 AM EDT US time, and support seems to have MANY requests for this advisory now and had to be refreshed twice to get to the Security Advisory). Microsoft is aksing ALL businesses to patch immediately, and ZDNet is expecting viruses and or trojans to become extant quickly so those with XP Pro need to patch also. XP Home is affected and needs to be patched also, but figure most here use Pro. Server 2003 is affected, 2000 Pro and servers also, and NT 4.0-- other than all of XP as operating system which is ALSO affected.
Please be warned here first. Blocking with firewalls can be done if you block RPC inbound and outbound (Microsoft has an article linked to in advisory with port numbers), but the patches probably are to prevent repercussions from doing so also adn all need to take note of this.
Admins may break thread off here if wanted, but please sticky it also unless you wish the thread topic to be handling recent RPC problems for more than one recent vulnerability that is now officially more than 4 (older ones exist also).
John-- who is tagging onto and expanding a thread, and absolutely not trying to hijack it.