rpc

[Bumble Bee]

Does anyone know waht rpc is? Remote procedure call and y? It restarts my computer and it seems to happen mostly when I activate the internet. It says it is being initiated by Nt activation system. Plick0rz Respond. I cant get my machmum like this.

Thats it. The end. No moe.

[LavisBlade]

IS THIS THE ERROR YOUR GETTING?

http://www.microsoft.com/security/images/system_shutdown.gif

IF YOU GET THIS ERROR YOU HAVE BLASTER WORM ON YOUR COMPUTER. One Nasty Bug!

GET RID OF IT AS FAST AS POSSIBLE!

If you need help removeing Microsoft has stuff that will help you

http://www.microsoft.com/security/incident/blast.asp

You can also go to Nortons site that goes into ALOT of detail... only go there if you have norton anti virus though...

http://www.sarc.com/avcenter/venc/data/w32.blaster.worm.html

[Kenshin]

spiffy what causes that is when you copy and past the blaster causes it to go thorugh the buffer repeatedly untill your computer's memory crashes.

the schools admin showed us the source code for the blaster.

[TeMpEsT]

You have been owned Bumble Bee.

[LavisBlade]

This is kind of late to get that worm... You should have downloaded that update the first day microsoft put it out.. I know I did.

ALWAYS download stuff when that little world pops up in the bottom right of your screen... It takes less then a minute to do. Most of the time it never downloads things anyway.

[Kenshin]

well if they got the counter-part to the blaster worm called the welcha it deletes the blaster from the computer automatically downloads the SR1 patch then patches the welcha over it which is the exact same thing as the blaster except it does that little extra bit to keep microsoft from fixing the problem.

[LavisBlade]

I always thought that the patch they sent out almost totally got rid of the RPC function because later versions of the Windows Os's (Win 98, 2000, Me) were not affected just because of the fact they didnt have the RPC.

[Kenshin]

the blaster does other stuff besides that crap just dunno what but still its annoying and bothersome. I think it ****s up your copy and paste shit still because when we had welcha our computer would still freeze when we did it it just would display the RPC. Finally Billish isolated it onto a computer which Geno decided to unleash on the network yestarday in an effort to show us how a dual monitor display works. Luckily now we have SR1 before the PC was hooked up to the network.

[WolfmanNCSU]

What the blaster does.....

When W32.Blaster.Worm is executed, it does the following:


Checks to see whether a computer is already infected and whether the worm is running. If so, the worm will not infect the computer a second time.


Adds the value:

"windows auto update"="msblast.exe"

to the registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run

so that the worm runs when you start Windows.


Generates an IP address and attempts to infect the computer that has that address. The IP address is generated according to the following algorithms:

For 40% of the time, the generated IP address is of the form A.B.C.0, where A and B are equal to the first two parts of the infected computer's IP address.

C is also calculated by the third part of the infected system's IP address; however, for 40% of the time the worm checks whether C is greater than 20. If so, a random value less than 20 is subtracted from C. Once the IP address is calculated, the worm will attempt to find and exploit a computer with the IP address A.B.C.0.

The worm will then increment the 0 part of the IP address by 1, attempting to find and exploit other computers based on the new IP address, until it reaches 254.


With a probability of 60%, the generated IP address is completely random.


Sends data on TCP port 135 that may exploit the DCOM RPC vulnerability. The worm sends one of two types of data: either to exploit Windows XP or Windows 2000.

For 80% of the time, Windows XP data will be sent; and for 20% of the time, the Windows 2000 data will be sent.

NOTES:
The local subnet will become saturated with port 135 requests.
While W32.Blaster.Worm cannot spread to the Windows NT or Windows Server 2003, unpatched computers running these operating systems may crash as a result of the worm's attempts to exploit them. However, if the worm is manually placed and executed on a computer running these operating systems, it can run and spread.
Due to the random nature of how the worm constructs the exploit data, this may cause the RPC service to crash if it receives incorrect data. This may manifest as svchost.exe, generating errors as a result of the incorrect data.
If the RPC service crashes, the default procedure under Windows XP and Windows Server 2003 is to restart the computer. To disable this feature, see step one of the Removal Instructions below.


Uses Cmd.exe to create a hidden remote shell process that will listen on TCP port 4444, allowing an attacker to issue remote commands on an infected system.


Listens on UDP port 69. When the worm receives a request from a computer to which it was able to connect using the DCOM RPC exploit, it will send msblast.exe to that computer and tell it to execute the worm.


If the current date is the 16th through the end of the month for the months of January to August, or if the current month is September through December, the worm will attempt to perform a DoS on Windows Update. However, the attempt to perform the DoS will succeed only if one the following conditions is true:
The worm runs on a Windows XP computer that was either infected or restarted during the payload period.
The worm runs on a Windows 2000 computer that was infected during the payload period and has not been restarted since it was infected.
The worm runs on a Windows 2000 computer that has been restarted since it was infected, during the payload period, and the currently logged in user is Administrator.


The DoS traffic has the following characteristics:
Is a SYN flood on port 80 of windowsupdate.com.
Tries to send 50 HTTP packets every second.
Each packet is 40 bytes in length.
If the worm cannot find a DNS entry for windowsupdate.com, it uses a destination address of 255.255.255.255.

Some fixed characteristics of the TCP and IP headers are:
IP identification = 256
Time to Live = 128
Source IP address = a.b.x.y, where a.b are from the host ip and x.y are random. In some cases, a.b are random.
Destination IP address = dns resolution of "windowsupdate.com"
TCP Source port is between 1000 and 1999
TCP Destination port = 80
TCP Sequence number always has the two low bytes set to 0; the 2 high bytes are random.
TCP Window size = 16384


The worm contains the following text, which is never displayed:

I just want to say LOVE YOU SAN!!
billy gates why do you make this possible ? Stop making money and fix your software!!

[Kenshin]

well imo the hackers are ****ing dumbasses. Do you know how many million lines of code there are in windows the only way to get a perfect product is to sell the product and patch the product as problems arise. Infact over half the problems wouldn't have to be patched if it weren't for hackers.

thanks for the info wolfman.

[WolfmanNCSU]

Yeah, peeps have different reasons for hacking, but it still makes things hard on all of us.

No prob, I always like to research bugs/viruses etc. To see what loop holes they find each time.

[Kenshin]

dude after talking with Brain our computer admin he wrote a program that uses the RPC to give remote computers admin power. He explained what service packet 1 did which was change a bunch of variabels and access points so that the virus wouldn't be able to find the RPC feature. Seems to me that if they can't get it to work they woudl remove it.

[8 Ball]

I had that mother ****er too. I hated that. The local computer shop took it off of my pc for me for free!!! Because I couldnt figure out how the hell to get rid of it. Maybe I should start updating because I never ****ing do.