Security
Interview with Rootkit Hunter author Michael Boelen
One of the greatest joys we Linux users have is to say to our Windows-running friends, family and co-workers that we do not suffer from viruses like they do. However, the reality is that we aren't immune from being attacked. There are plenty of nasty things out there that would be happy to trash our systems. One of these nasty things is something called a rootkit. Rootkits allow a cracker to ensure future access to a compromised system while hiding the evidence from administrators and users; see LWN's look at the Adore rootkit for an example.
So how do you detect them? One way is to use the tool Rootkit Hunter. The following is an interview with the author of this utility, Michael Boelen.
Joe Klemmer: Tell us a bit about yourself. Who is Michael Boelen?
My main interests are networking, hardware, security and small application development. As many people, I like to read, but especially interested in computer related stuff.
JK: What led you into system security?
JK: What, specifically, are rootkits?
Because rootkits are unwanted and difficult to find without good searching, automated tools are being created. Although an UNIX specialist is often able to find bad things better/quicker than automated tools, it can be a very valuable tool. Of course it is a nice addition to UNIX specialists, but also for average UNIX users which aren't able to find out with things of a UNIX system are good or evil (like hidden files, bad strings, not usual network ports etc).
JK: You've said elsewhere that you built rkhunter because you didn't find the existing tools to your liking. What was it about them that you felt needed changing?
JK: Over the course of rkhunter's evolution, have you found anything interesting about root kits? Any similarities or differences? Are there any trends?
Most tools use the same approach, so I tried to combine as many as possible ways to detect these suspicious traces. And although it gets better every release, a lot of things have to be done.
Rootkits don't have a 'normal' trend like viruses/worms have, because viruses aren't often used for a single person to achieve his goal (beside breaking up systems, sending spam or planting a trojan). In fact, some individuals create rootkits for their needs at the moment they need them. These custom made rootkits contain often simple things like IRC bots, backdoors and sniffers. Within the next few months, those things will be getting special attention from me and added to Rootkit Hunter. Rootkits won't quickly disappear, so the war isn't yet over.
JK: Do you know if rkhunter has had an impact on the root kit community? Are they now trying to design kits to work around rkhunter?
JK: I would guess that the battle between the root kit "developers" and the security community is similar to the anti-virus wars. Is the bulk of your work spent in catching up to new root kits? Or are you in a position of developing preemptive technologies to head off the kit builders?
JK: What do you see for the future of rkhunter? With the advent of SElinux will there still be a need for rkhunter and it's kind?
This interview gives me the opportunity to ask people an easy question: If you find something interesting for me, can you send it to me?
The question above gives an answer to your question, because although I can improve Rootkit Hunter a lot, I really need input from the users and the guys on the field. Rootkits, sniffers, ideas and even books are needed to keep on improving. Till now I have already got a lot of input, but I still need more information. So have a simple thought about the future: it only will be better, but only if I get support from the community!
New vulnerabilities
apache: protected pages vulnerability
Package(s): | apache | CVE #(s): | CAN-2004-0811 | ||||||||
Created: | September 23, 2004 | Updated: | September 29, 2004 | ||||||||
Description: | Apache 2.0.51 may allow the viewing of protected pages because of a problem merging the Satisfy directive. | ||||||||||
Alerts: |
|
getmail: filesystem overwrite vulnerability
Package(s): | getmail | CVE #(s): | CAN-2004-0880 CAN-2004-0881 | ||||||||||||
Created: | September 23, 2004 | Updated: | October 4, 2004 | ||||||||||||
Description: | Getmail has a vulnerability that may allow a local user to create or overwrite files in any directory on the system. | ||||||||||||||
Alerts: |
|
jabberd: remote denial of service vulnerability
Package(s): | jabberd | CVE #(s): | |||||
Created: | September 23, 2004 | Updated: | September 29, 2004 | ||||
Description: | Jabberd's XML parsing routines have a vulnerability that may be exploited to create a remote denial of service. | ||||||
Alerts: |
|
sendmail: pre-set password
Package(s): | sendmail | CVE #(s): | CAN-2004-0833 | ||||
Created: | September 27, 2004 | Updated: | September 29, 2004 | ||||
Description: | Hugo Espuny discovered a problem in sendmail, a commonly used program to deliver electronic mail. When installing "sasl-bin" to use sasl in connection with sendmail, the sendmail configuration script use fixed user/pass information to initialize the sasl database. Any spammer with Debian systems knowledge could utilize such a sendmail installation to relay spam. | ||||||
Alerts: |
|
subversion: metadata information disclosure
Package(s): | subversion | CVE #(s): | CAN-2004-0749 | ||||||||||||
Created: | September 23, 2004 | Updated: | November 4, 2004 | ||||||||||||
Description: | The subversion version control system has vulnerabilities in the handling of metadata such as log file entries related to using mod_authz_svn. | ||||||||||||||
Alerts: |
|
Page editor: Jonathan Corbet
Next page:
Kernel development>>