29
May
Posted in Windows by carlosap |
Windows Vista Vulnerable to StickyKeys Backdoor
Monday March 12, 2007 at 8:11 am CST
Posted by Vinoo Thomas
Trackback
StickyKeys is an accessibility feature to aid handicapped users. It allows the user to press a modifier key, such as the Shift key, and have it remain active until another key is pressed. StickyKeys is activated by pressing the shift key or a modifier key five times in sequence and a beep is sounded. Sounds innocuous, right? Dead wrong!
Apparently, Windows Vista does not check the integrity of the file that launches StickyKeys “c:/windows/system32/sethc.exe” before executing it. Which means you could replace it with another executable and run it by depressing the shift key five times. A popular replacement is “cmd.exe.” After replacement, one could invoke this command prompt at the login prompt without the need to authenticate as shown in the below screenshot.
Invoking Sticky Keys
Once launched, it is possible to execute explorer.exe without authenticating and get a full desktop running under the credentials of the NT Authority\system account. And from this point on an attacker has full access to the system.
Launching desktop via Sticky Keys
This legacy backdoor method is not something new–Win 2000 and XP are also vulnerable. Applying the latest Windows updates insures that “sethc.exe” is protected by Windows file protection. In Vista replacing system files is a more difficult because of Trusted Installer. However, running the following two commands nullifies this.
takeown /f c:\windows\system32\sethc.exe
cacls c:\windows\system32\sethc.exe /G administrator:F
To execute the above commands successfully, it requires an administrator to be logged in; but a determined attacker can always find workarounds to exploit this built-in backdoor. In fact once a command prompt is obtained via this method, we can use it to create a new user, add this user to the administrators group via the net command and then use this account to rightfully log in using the following commands.
net user USERNAME /add
net localgroup administrators USERNAME
One can always argue that an attacker actually needs access to the machine to be able to pull this off. Of all the unauthorized system access incidents that organizations reported last year, roughly 27% were by internal employees. And it is this threat from within (disgruntled or naughty employees) that poses the greatest computer security threat to organizations today.
Another alarming feature of this backdoor is that an attacker can use this method to bypass login on terminal servers and workstations with the remote desktop enabled. Since no third-party tools are being installed on the system and we are using Microsoft’s own files to achieve this, it will be difficult to detect for a typical administrator.
Perhaps one can uninstall the Accessibility Tools feature, which is installed by default to avoid this fairly simple, yet potentially serious built-in backdoor. And don’t forget to hit the shift key five times and see what pops up on your desktop.
28
May
Posted in CentOS by carlosap |
http://www.alcancelibre.org/staticpages/index.php/SAMBALDAP-CENTOS5
28
May
Posted in debian / ubuntu by carlosap |
http://www.ruf.rice.edu/~rlug/help/tips-ssh.html
Use this on Debian based boxes:
Use update-rc.d to create the symlinks to the appropriate runlevel directories.
update-rc.d -f ssh defaults 20
Since there are tons of brute force attacks against SSH captured by DenyHosts:
http://stats.denyhosts.net/stats.html
I’d consider it a bad idea to allow remote ssh (ie. via the external interface) to the Untangle ssh server (ie. if you have either manually symlinked /etc/rc3.d/… and /etc/rc5.d/… to /etc/init.d/ssh or have enabled the “Config -> Support -> Allow Untangle Support…” option).
The easiest way to secure the SSH server on Untangle is to bind the server to the LAN (internal interface) IP address rather than the default (which is all interfaces). To do so:
Quote:
| ssh root@your_untangle_server
vi /etc/ssh/sshd_config
add a line:
ListenAddress 192.168.1.1
save the file.
restart ssh:
/etc/init.d/ssh restart |
Replace 192.168.1.1 (above) with the internal IP address of your Untangle server.
After restarting ssh, you can connect to it from your internal network but not from the internet such that it won’t be subject to brute force password attacks.
Note: Untangle support will not be able to access your Untangle server so if you rely on their support efforts, don’t do this (or do it and if you need their support, remember to comment out the ListenAddress line and restart ssh).
For extra security:
If you’ve setup other users on Untangle (ie. using useradd from the command line or similar), it’s usually a good idea to set
“PermitRootLogin no” in /etc/ssh/sshd_config to prevent users from logging in as root (since everybody knows that the ssh server has a root account). You may require root access so you’ll need to use “sudo” after you login as non-root. This may be overkill if you’ve restricted external access (as described above) and your LAN is trusted.
23
May
Posted in Blog Personal by carlosap |
http://www.revver.com/video/693534/17-tareas-posteriores-a-la-instalacion-de-active-directory/
22
May
Posted in CentOS, Fedora by carlosap |
Hi Folks,
I’ve searched throught this board and noticed a few folks have had this problem…Mine
started after installing an ethernet card….Screen came up blue…..”Registry file
failure. The registry cannot load the hive file System Root\System32\Config\Software
I found this apparent fix when booting from the Windows XP cd….
Quote:
Do you have a XP CD? If so, boot into the recovery console from it and type the following:
cd system32
cd config
ren software software.bak
ren system system.bak
cd ..
cd ..
cd repair
copy software c:\windows\system32\config
copy system c:\windows\system32\config
This restores XP to brand new. You have all data, but a fresh registry. Whatever
you do, DON’T REBOOT UNTIL YOU’RE DONE WHATEVER YOU’RE DOING!!! It will probably
die again.
End of Quote
The problem is that I’m not that great with computers and I followed the wording
EXACTLY…After the first entries I come to
“ren software software.bak” which after I have changed to the Config directory says
“the system cannot find the file or directory specified…I think I’m missing something
here…I just typed “cd..” like it said etc..and it said the same thing..Can someone
clarify EXACTly how this should be typed in in the recovery part of the cd? I also
note it says copy software c:\windows\system32\config
….I have Xp on a d drive (the recovery mode notes the file as D:WinXP
So I assume I should type “d:\winxp\system32 etc….instead?
I have 2 hard drives..the first being a tiny 540k which runs Win95 in emergencies
like this but is pretty useless otherwise…Can someone sort this out for me or suggest
other fixes for this dreaded registry problem…Very depressing..
Thank you for your time.
Kevin
14
May
Posted in Blog Personal by carlosap |
Cisco IOS Software, C3550 Software (C3550-IPBASE-M), Version 12.2(25)SEB4, RELEASE SOFTWARE (fc1)
Copyright (c) 1986-2005 by Cisco Systems, Inc.
Compiled Tue 30-Aug-05 13:14 by yenanh
12
May
Posted in CentOS by carlosap |
Configuring bridges for multiple VLANs
This section will be beefed up a bit later. I’m rushing it out due to popular demand!
Read more… »
12
May
Posted in CentOS by carlosap |
How do I configure my Red Hat Enterprise Linux 3 system to use 802.1q Virtual Local Area Network (VLAN) tagging for all network communication?
4
May
Posted in Blog Personal by carlosap |
http://www.meebo.com
2
May
Posted in CentOS by carlosap |
CentOS 5 (Red Hat-based). I’m connecting to a Cisco Router via serial cable.
1) run ‘minicom -s’ first, to enter configuration mode, you’ll open a text-based menu. Note: Use “ENTER” to exit any menus except the main menu.
2) Under “Serial Port Setup” mine was set to default /dev/modem and 38400. I had to manually change it to 9600 and set the device to /dev/ttyS0. Remember to hit ENTER to exit, do NOT try to use “Q” to “Quit”, if you’re under the speed/parity selection window that’ll change your parity to 2 (this is where I learned that, heh).
3) Go under “Modem and Dialing” and remove the “Init String”. Anything in this field will be sent to the device when you connect. The default AT string won’t bother a Cisco device as far as I know, especially if it’s not in enabled or in config mode when you connect, but it’s kinda annoying to have it pop up on connect.
4) From the main menu use “Save setup to DFL” to create a new config file for minicom.
Buscamos donde esta minicom con:
# which minicom
/usr/bin/minicom
Miramos sus permisos de minicom con:
# ls -la /usr/bin/minicom
Salen q permiten al grupo uucp
Editamos /etc/group y ponemos al usuario juanito en el grupo uucp
Miramos sus permisos de /dev/ttyS0:
# ls -la /dev/ttyS0
Salen q permiten al grupo tty
Editamos /etc/group y ponemos al usuario juanito en el grupo tty
Damos permisos de lectura y escritura a /dev/ttys0 con:
# chmod 666 /dev/ttys0