I saw the price of silver today (over $14/ounce) and I recalled that I have an actual silver quarter dollar. Back when I first found it, it was worth 59¢ (just in terms of silver content). On a lark, I recalculated the value today, and it came out worth a bit over $1.90, just in terms of silver content, enough for a cup of coffee.
/* * expand_stack SMP race local root exploit * * Copyright (C) 2005 Christophe Devine and Julien Tinnes * * This program is quite unreliable - you may have to run it * several times before getting a rootshell. It was only tested * so far on a bi-xeon running Debian testing / Linux 2.4.29-rc1. * * Vulnerability discovered by Paul Starzetz <ihaquer at isec.pl> * http://www.isec.pl/vulnerabilities/isec-0022-pagefault.txt
Nice try, I'll give them that.
I got a call from Dan the Network engineer that a machine I manage had registered a large network spike overnight. When I heard that it was a large spike from the machine, I knew it wasn't a DoS attack, but was probably participating in one.
I unplugged the machine from the network then logged in from the console. I was able to find the rouge process (masquerading as an Apache process—nice job!) listening in one some randomly picked port, giving anyone that connected to that port a commande line:
#!/usr/bin/perl # Telnet-like Standard Daemon 1.0 # # Dark_Anjo - firstname.lastname@example.org # - email@example.com # - www.xn.rg3.net # - www.red.not.br/xn # # For those guys that still like to open ports # and use non-rooted boxes # # This has been developed to join in the TocToc # project code, now it's done and I'm distributing # this separated # # This one i made without IO::Pty so it uses # only standard modules... enjoy it # # tested on linux boxes.. probably will work fine on others # any problem... #firstname.lastname@example.org #
But fortunately, the exploit (quoted at the top) didn't work on the machine so the shell obtained was a non-root shell.
Apparently, the customer account information was leaked and the crackers were able to FTP their scripts onto the server. Not much that can be done about that, other than telling the customer to keep a tighter lid on their login information.
And as I like to remind myself, it could have been worse …