ich werde dir mal einen gefallen tun und dir zum thema lsas und schadsoftware einen text pasten - von symantec.
zitat:
When W32.Sasser.Worm runs, it does the following:
Attempts to create a mutex named Jobaka3l and exits if the attempt fails. This ensures that no more than one instance of the worm can run on the computer at any time.
Copies itself as %Windir%\avserve.exe.
--------------------------------------------------------------------------------
Note: %Windir% is a variable. The worm locates the Windows installation folder (by default, this is C:\Windows or C:\Winnt) and copies itself to that location.
--------------------------------------------------------------------------------
Adds the value:
"avserve.exe"="%Windir%\avserve.exe"
to the registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
so that the worm runs when you start Windows.
Uses the AbortSystemShutdown API to hinder attempts to shut down or restart the computer.
Starts an FTP server on TCP port 5554. This server is used to spread the worm to other hosts.
Retrieves the IP addresses of the infected computer, using the Windows API, gethostbyname.
--------------------------------------------------------------------------------
Note: The worm will ignore any of the following IP addresses:
127.0.0.1
10.x.x.x
172.16.x.x - 172.31.x.x (inclusive)
192.168.x.x
169.254.x.x
--------------------------------------------------------------------------------
Generates another IP address, based on one of the IP addresses retrieved from the infected computer.
25% of the time, the last two octets of the IP address are changed to random numbers. For example, if A.B.C.D is the IP address retrieved in step 6, C and D will be random.
23% of the time, the last three octets of the IP address are changed to random numbers. For example, if A.B.C.D is the IP address retrieved in step 6, B, C, and D will be random.
52% of the time, the IP address is completely random.
--------------------------------------------------------------------------------
Notes:
Because the worm creates a completely random addresses 52% of the time, any IP address can be infected, including those ignored in step 6.
This process is made up of 128 threads, which demands a lot of CPU time. As a result, an infected computer may become so slow and barely usable.
--------------------------------------------------------------------------------
Connects to the generated IP address on TCP port 445 to determine if a remote computer is online.
If a connection is made to a remote computer, the worm will send shell code to it, which may cause it to open a remote shell on TCP port 9996.
Creates a ftp script file cmd.ftp on the attacked computer.
Uses the shell on the remote computer to reconnect to the infected computer's FTP server, running on TCP port 5554, and retrieve a copy of the worm. This copy will have a name consisting of four or five digits, followed by _up.exe. For example, 74354_up.exe.
The Lsass.exe process will crash after the worm exploits the Windows LSASS vulnerability. Windows will display the alert and shut down the system in one minute.
Deletes cmd.ftp on the attacked computer. If the exploit code process is halted, cmd.ftp will remain on the attacked computer.
Creates a file at C:\win.log that contains the IP address of the computer that the worm most recently attempted to infect, as well as the number of infected computers.
Symantec Gateway Security 5400 Series and Symantec Gateway Security v1.0
Antivirus component: An update for the Symantec Gateway Security AntiVirus engine to protect against the W32.Sasser.Worm is now available. We advise Symantec Gateway Security 5000 Series users to run LiveUpdate.
IDS/IPS component: A signature for the Symantec Gateway Security 5400 Series that detects attacks against the Microsoft LSASS vulnerability was included in SU 8 released on April 14. A signature to detect the attacks against the Microsoft LSASS vulnerability on SGS v1.0 has been released. We advise Symantec Gateway Security 5000 Series users to run LiveUpdate.
Full application inspection firewall component: By default, Symantec's full application inspection firewall technology protects against the W32.Sasser.Worm by blocking attackers from accessing TCP/445, and the backdoor ports on infected systems (TCP/5554, TCP/9996). We urge Administrators to verify that their security policies do not allow inbound traffic to those ports.
Symantec Enterprise Firewall 8.0
By default, Symantec's full application inspection firewall technology protects against the W32.Sasser.Worm by blocking attackers from accessing TCP/445, and the backdoor ports on infected systems (TCP/5554, TCP/9996). We urge Administrators to verify that their security policies do not allow inbound traffic to those ports.
Symantec Enterprise Firewall 7.0.x and Symantec VelociRaptor 1.5
By default, Symantec's full application inspection firewall technology protects against the W32.Sasser.Worm by blocking attackers from accessing TCP/445, and the backdoor ports on infected systems (TCP/5554, TCP/9996). We urge Administrators to verify that their security policies do not allow inbound traffic to those ports.
Symantec Clientless VPN Gateway 4400 Series
This threat does not affect Symantec Clientless VPN Gateway v5.0. By default, the security gateway blocks access to TCP ports 445, 5554, and 9996.
Symantec Gateway Security 300 Series
By default, Symantec's stateful inspection firewall technology prevents an attacker from accessing TCP/445 on internal systems and the backdoor ports on infected systems (TCP 5554, 9996). We urge Administrators to verify that their security policy does not allow TCP/445, TCP/5554, TCP/9996 inbound and to use the AVpe feature of the SGS 300 series to make sure that all their antivirus clients are up-to-date with the most current virus definitions.
Symantec Firewall/VPN 100/200 Series
By default, Symantec's stateful inspection firewall technology prevents an attacker from accessing TCP/445 on internal systems and the backdoor ports on infected systems (TCP/5554, TCP/9996).
Symantec Client Security
Symantec has released a patch for Symantec Client Security 1.x and 2.0 that will identify the LSASS exploit with the MS_Windows_LSASS_RPC_DS_Request signature present in the infection attempt. If the Sasser worm application already exists on the system, all versions of Symantec Client Security with the default firewall policy will prompt the user to Permit/Block/Configure a rule for the worm when it tries to start the FTP server and send outbound data.
Virus definitions that provide protection against the worm are available through LiveUpdate or Intelligent Updater as of May 1, 2004.
Symantec Security Response offers these suggestions on how to configure Symantec products in order to minimize your exposure to this threat.
zitat ende.
du sagtest:
>>>>>>>>>wenn ein wurm eine schwachstelle im system angreift - zb LSASS - dann kann eine firewall diese schwachstelle erfolgreich schließen. ...wenn sie denn vernünftig konfiguriert wurde
Das ist Faslch, aber wirklich, bloedsinniger bloedsinn.
aha. dann wird symantec sich wie alle anderen experten wohl irren und du - prosecco - wirst recht haben.
oder?
GarfTermy
