Originally posted by captiva
reply to post by johnsky
Even encrypted I would be kinda wary of something called plans to kill !
All you need to do is be aware. There isnt a key-logger I know that wont be found by any active virus checker.
To be hacked, you need to be conned into being hacked. On-line transactions etc are unsafe and you should not be giving your info to anyone.
The only thing that should be sacred is your anonimity. Build it, protect it.
Respects
Sorry, you are VERY mistaken and have not the slightest idea of how cracking a system is done. I have been in the security field since I was thirteen
years old, and I am now twenty four. I assure you that there is many ways to get into a system that does not require the user to install a trojan.
portbind shellcode, executed via remote stack overflow found in whatever service someone finds a fault in. This requires you to do NOTHING and you are
wide open to having someone full control over you system. Look up the MS08-067 security vulnerability when you get a chance. Before this was patched,
and chances are there are still many systems that are affected, it allowed you full access to any Windows system without some lame method of having to
download a trojan on your target system.
This is a remote code execution vulnerability. An attacker who successfully exploited this vulnerability could take complete control of an affected
system remotely. On Microsoft Windows 2000-based, Windows XP-based, and Windows Server 2003-based systems, an attacker could exploit this
vulnerability over RPC without authentication and could run arbitrary code. If an exploit attempt fails, this could also lead to a crash in
Svchost.exe. If the crash in Svchost.exe occurs, the Server service will be affected. The Server service provides file, print, and named pipe sharing
over the network.
The vulnerability is caused by the Server service, which does not correctly handle specially crafted RPC requests.
So with a little programming knowledge, the ability to use a debugger such as gdb, general knowedge of overflows, add in some shellcode, and you have
yourself a remotely exploitable peice of code, unrestricted access to any system you desire.
example:
Usage: ./code -target ip- -OS-
Example: ./exploit.pl 192.168.1.1 2
Select OS Version
[-]Windows 2000: OS Version = 1
[-]Windows 2003[SP2]: OS Version = 2
[-]Windowx XP[SP2]: OS Version = 3
result:
Exploit sent to target successfully... Telnet to port 4444.
So I then telnet to port 4444 (or whatever I programmed the shellcode to start up the portbind on) and am greeted with a wonderful command prompt that
has full control over your system.
There exists MANY security vulnerabilities that work just as this one has shown and there is nothing you can do about it but to patch them as soon as
possible. Also, this has been released and there still exists many, many systems that fall victim to this exact exploit. As for unreleased code, that
is a whole new world and requires very little work to crack a system. I have zero days that friends and I have written that would work on the majority
of systems if we felt the need. You obviously have been living under a rock when it comes to the field of system security. No system is safe unless it
is disconnected from the internet completely.
[edit on 1/4/2009 by deadline527]
[edit on 1/4/2009 by deadline527]