Account Options

  1. Sign in
The old Google Groups will be going away soon.
Switch to the new Google Groups.
Google Groups Home
« Groups Home
Internet VIRUS alert
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
  5 messages - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Peter E. Yee  
View profile  
 More options Nov 3 1988, 2:28 am
Newsgroups: comp.protocols.tcp-ip
From: y...@AMES.ARC.NASA.GOV (Peter E. Yee)
Date: 3 Nov 88 07:28:00 GMT
Subject: Internet VIRUS alert
We are currently under attack from an Internet VIRUS.  It has hit UC Berkeley,
UC San Diego, Lawrence Livermore, Stanford, and NASA Ames.  The virus comes in
via SMTP, and then is able to attack all 4.3BSD and SUN (3.X?) machines.  It
sends a RCPT TO that requests that its data be piped through a shell.  It copies
in a program, compiles and executes it.  This program copies in VAX and SUN
binaries that try to replicate the virus via connections to TELNETD, FTPD,
FINGERD, RSHD, and SMTP.  The programs also appear to have DES tables in them.
They appear in /usr/tmp as files that start with the letter x.  Removing them
is not enough as they will come back in the next wave of attacks.  For now
turning off the above services seems to be the only help.  The virus is able
to take advantage of .rhosts files and hosts.equiv.  We are not certain what the
final result of the binaries is, hence the warning.

I can be contacted at (415) 642-7447.  Phil Lapsley and Kurt Pires at this
number are also conversant with the virus.  

                                                        -Peter Yee
                                                        y...@ames.arc.nasa.gov
                                                        ames!yee


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Rick Adams  
View profile  
 More options Nov 3 1988, 10:59 am
Newsgroups: comp.protocols.tcp-ip
From: r...@SEISMO.CSS.GOV (Rick Adams)
Date: 3 Nov 88 15:59:11 GMT
Local: Thurs, Nov 3 1988 10:59 am
Subject: Re: Internet VIRUS alert
Please install this patch from Berkeley if you are running sendmail.

---rick

From bos...@okeeffe.Berkeley.EDU Thu Nov  3 06:38:39 1988
Received: from okeeffe.Berkeley.EDU by beno.CSS.GOV (5.59/5.17)
        id AA03506; Thu, 3 Nov 88 06:38:26 EST
Received: by okeeffe.Berkeley.EDU (5.61/1.29)
        id AA22190; Thu, 3 Nov 88 02:58:55 PST
Date: Thu, 3 Nov 88 02:58:55 PST
From: bos...@okeeffe.Berkeley.EDU (Keith Bostic)
Message-Id: <8811031058.AA22190@okeeffe.Berkeley.EDU>
To: r...@beno.CSS.GOV, s...@purdue.edu
Subject: Virus (READ THIS IMMEDIATELY)
Status: RO

Guys, if you could post this to whatever appropriate newsgroups,
as soon as possible, we'd appreciate it.

Thanks.

--keith

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Subject: Fixes for the virus
Index: usr.lib/sendmail/src/srvrsmtp.c 4BSD

Description:
        There's a virus running around; the salient facts.  A bug in
        sendmail has been used to introduce a virus into a lot of
        Internet UNIX systems.  It has not been observed to damage the
        host system, however, it's incredibly virulent, attempting to
        introduce itself to every system it can find.  It appears to
        use rsh, broken passwords, and sendmail to introduce itself
        into the target systems.  It affects only VAXen and Suns, as
        far as we know.  

        There are three changes that we believe will immunize your
        system.  They are attached.

        Thanks to the Experimental Computing Facility, Center for
        Disease Control for their assistance.  (It's pretty late,
        and they certainly deserved some thanks, somewhere!)

Fix:
        First, either recompile or patch sendmail to disallow the `debug'
        option.  If you have source, recompile sendmail after first
        applying the following patch to the module svrsmtp.c:

                *** /tmp/d22039 Thu Nov  3 02:26:20 1988
                --- srvrsmtp.c  Thu Nov  3 01:21:04 1988
                ***************
                *** 85,92 ****
                        "onex",               CMDONEX,
                  # ifdef DEBUG
                        "showq",      CMDDBGQSHOW,
                -       "debug",      CMDDBGDEBUG,
                  # endif DEBUG
                  # ifdef WIZ
                        "kill",               CMDDBGKILL,
                  # endif WIZ
                --- 85,94 ----
                        "onex",               CMDONEX,
                  # ifdef DEBUG
                        "showq",      CMDDBGQSHOW,
                  # endif DEBUG
                + # ifdef notdef
                +       "debug",      CMDDBGDEBUG,
                + # endif notdef
                  # ifdef WIZ
                        "kill",               CMDDBGKILL,
                  # endif WIZ

        Then, reinstall sendmail, refreeze the configuration file,
        using the command "/usr/lib/sendmail -bz", kill any running
        sendmail's, using the ps(1) command and the kill(1) command,
        and restart your sendmail.  To find out how sendmail is
        execed on your system, use grep(1) to find the sendmail start
        line in either the files /etc/rc or /etc/rc.local

        If you don't have source, apply the following patch to your
        sendmail binary.  SAVE A COPY OF IT FIRST, IN CASE YOU MESS
        UP!  This is mildly tricky -- note, some versions of strings(1),
        which we're going to use to find the offset of the string
        "debug" in the binary print out the offsets in octal, not
        decimal.  Run the following shell line to decide how your
        version of strings(1) works:

                /bin/echo 'abcd' | /usr/ucb/strings -o

        Note, make sure the eight control 'G's are preserved in this
        line.  If this command results in something like:

                0000008 abcd

        your strings(1) command prints out locations in decimal, else
        it's octal.

        The patch script for sendmail.  NOTE, YOUR OFFSETS MAY VARY!!
        This script assumes that your strings(1) command prints out
        the offsets in decimal.  

                Script started on Thu Nov  3 02:08:14 1988
                okeeffe:tmp {2} strings -o -a /usr/lib/sendmail | egrep debug
                0096972 debug
                okeeffe:tmp {3} adb -w /usr/lib/sendmail
                ?m 0 0xffffffff 0
                0t10$d
                radix=10 base ten
                96972?s
                96972:          debug
                96972?w 0
                96972:          25701   =       0
                okeeffe:tmp {4} ^D
                script done on Thu Nov  3 02:09:31 1988

        If your strings(1) command prints out the offsets in octal,
        change the line "0t10$d" to "0t8$d".

        After you've fixed sendmail, move both /bin/cc and /bin/ld to
        something else.  (The virus uses the cc and the ld commands
        to rebuild itself to run on your system.)

        Finally, kill any processes on your system that don't belong there.
        Suspicious ones have "(sh)" or "xNNNNNNN" where the N's are random
        digits, as the command name on the ps(1) output line.

        One more thing, if you find files in /tmp or /usr/tmp that
        have names like "xNNNNNN,l1.c", or "xNNNNNN,sun3.o", or
        "xNNNNNNN,vax.o" where the N's are random digits, you've been
        infected.


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Jerry Scott  
View profile  
 More options Nov 3 1988, 11:37 am
Newsgroups: comp.protocols.tcp-ip
From: je...@TWG.COM (Jerry Scott)
Date: 3 Nov 88 16:37:00 GMT
Subject: RE: Internet VIRUS alert
Peter,
        I guess I am not that familiar with the Unix mail systems
of the Sun and Vax.  Is this sendmail?  Does sendmail have the ability
of receiving mail for a process?  If so, this is the biggest security
hole I have heard about in a long time.

Jerry


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Moses Mason  
View profile  
 More options May 29 2011, 7:09 am
Newsgroups: comp.protocols.tcp-ip
From: Moses Mason <moses.ma...@gmail.com>
Date: Sun, 29 May 2011 04:09:26 -0700 (PDT)
Local: Sun, May 29 2011 7:09 am
Subject: Re: Internet VIRUS alert
Good luck~


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Barry Margolin  
View profile  
 More options May 29 2011, 7:06 pm
Newsgroups: comp.protocols.tcp-ip
From: Barry Margolin <bar...@alum.mit.edu>
Date: Sun, 29 May 2011 19:06:23 -0400
Local: Sun, May 29 2011 7:06 pm
Subject: Re: Internet VIRUS alert
In article
<7e2cc8b4-2fe0-47f9-9e4b-ae56f4c0a...@glegroupsg2000goo.googlegroups.com
>,

 Moses Mason <moses.ma...@gmail.com> wrote:

> Good luck~

Did you notice the date of the message?  I think they might be out of
the wood by now.

> On Thursday, November 3, 1988 3:28:00 PM UTC+8, Peter E. Yee wrote:

--
Barry Margolin, bar...@alum.mit.edu
Arlington, MA
*** PLEASE don't copy me on replies, I'll read them in the group ***

 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »