March 1995 - Test - lists.nanog.org

VB-95:01 - HP Security Vulnerability in Remote Watch
by CERT Bulletin 02 Mar '95

02 Mar '95

CERT Vendor-Initiated Bulletin VB-95:01 March 2, 1995 Topic: Security Vulnerability in Remote Watch Source: Hewlett-Packard Company To aid in the wide distribution of essential security information, the CERT Coordination Center is forwarding the following information from Hewlett-Packard. Hewlett-Packard urges you to act on this information as soon as possible. Their contact information is included in the forwarded text below; please contact them if you have any questions or need further information. ========================FORWARDED TEXT STARTS HERE============================ ------------------------------------------------------------------------- HEWLETT-PACKARD SECURITY BULLETIN: #00020, 31 January 95 ------------------------------------------------------------------------- Hewlett-Packard recommends that the information in the following Security Bulletin should be acted upon as soon as possible. Hewlett- Packard will not be liable for any consequences to any customer resulting from customer's failure to fully implement instructions in this Security Bulletin as soon as possible. _______________________________________________________________________ PROBLEM: Security vulnerability in Remote Watch in fileset WATCH-RUN for releases of HP-UX. PLATFORM: HP 9000 series 300/400s & 700/800s running HP-UX revisions 8.X, 9.X. DAMAGE: A vulnerability in Remote Watch exists allowing users to potentially gain increased privileges. SOLUTION: Apply patch PHSS_5136 (series 800 , HP-UX 9.X), or PHSS_5185 (series 800 , HP-UX 8.X), or PHSS_5107 (series 700 , HP-UX 9.X), or PHSS_5180 (series 700 , HP-UX 8.X), or PHSS_5120 (series 300/400, HP-UX 9.X), or PHSS_5168 (series 300/400, HP-UX 8.X). AVAILABILITY: All patches are available now. _______________________________________________________________________ I. Update A. It has been found that HP-UX systems with Remote Watch installed have this vulnerability. The vulnerability allows users to potentially gain increased privileges. If these patches are installed, then the vulnerability cannot be exploited. B. Fixing the problem The vulnerability can be eliminated from releases 8.X and 9.X of HP-UX by applying a patch. Hewlett-Packard recommends that all customers concerned with the security of their HP-UX systems apply the appropriate patch as soon as possible. C. How to Install the Patch (for HP-UX 8.X and 9.X) 1. Determine which patch is appropriate for your hardware platform and operating system: PHSS_5136 (series 800 , HP-UX 9.X), PHSS_5185 (series 800 , HP-UX 8.X), PHSS_5107 (series 700 , HP-UX 9.X), PHSS_5180 (series 700 , HP-UX 8.X), PHSS_5120 (series 300/400, HP-UX 9.X), PHSS_5168 (series 300/400, HP-UX 8.X), 2. Hewlett Packard's HP-UX patches are available via email and WWW (MOSAIC) To obtain a copy of the HP SupportLine email service user's guide, send the following in the TEXT PORTION OF THE MESSAGE to support(a)support.mayfield.hp.com (no Subject is required): send guide The users guide explains the process for downloading HP-UX patches via email and other services available. WWW (MOSAIC) service (downloading of patches) is also available via WWW (MOSAIC) our URL is: (http://support.mayfield.hp.com) 3. Apply the patch to your HP-UX system. 4. Examine /tmp/update.log for any relevant WARNINGs or ERRORs. This can be done as follows: a. At the shell prompt, type "tail -60 /tmp/update.log | more" b. Page through the next three screens via the space bar, looking for WARNING or ERROR messages. D. Impact of the patch and workaround No patches will be available for versions of HP-UX prior to 8.0. E. To subscribe to automatically receive future NEW HP Security Bulletins from the HP SupportLine mail service via electronic mail, send an email message to: support(a)support.mayfield.hp.com (no Subject is required) Multiple instructions are allowed in the TEXT PORTION OF THE MESSAGE, here are some basic instructions you may want to use: To add your name to the subscription list for new security bulletins, send the following in the TEXT PORTION OF THE MESSAGE: subscribe security_info To retrieve the index of all HP Security Bulletins issued to date, send the following in the TEXT PORTION OF THE MESSAGE: send security_info_list WWW (MOSAIC) service (Browsing of Bulletins) is also available via WWW (MOSAIC) our URL is: (http://support.mayfield.hp.com) Choose "Support News", then under Support News, choose "Security Bulletins" F. To report new security vulnerabilities, send email to: security-alert(a)hp.com =========================FORWARDED TEXT ENDS HERE============================= CERT bulletins, CERT advisories, information about FIRST representatives, and other information related to computer security are available for anonymous FTP from info.cert.org. CERT advisories and bulletins are also posted on the USENET newsgroup comp.security.announce. If you would like to have future advisories and bulletins mailed to you or to a mail exploder at your site, please send mail to cert-advisory-request(a)cert.org. If you wish to send sensitive incident or vulnerability information to CERT staff by electronic mail, we strongly advise that the e-mail be encrypted. The CERT Coordination Center can support a shared DES key, PGP (public key available via anonymous FTP on info.cert.org) or PEM (contact CERT staff for details). Internet E-mail: cert(a)cert.org Telephone: +1 412-268-7090 (24-hour hotline) CERT personnel answer 8:30 a.m.-5:00 p.m. EST(GMT-5)/EDT(GMT-4), and are on call for emergencies during other hours. Fax: +1 412-268-6989 CERT Coordination Center Software Engineering Institute Carnegie Mellon University Pittsburgh, PA 15213-3890 USA CERT is a service mark of Carnegie Mellon University.

1 0

Re: 60 Day Termination Notice (fwd)
by Sean Doran 02 Mar '95

02 Mar '95

>We've already ordered a backhoe - we figure we can take out the T3 and >bury the ENSS at the same time :-) Don't you need an environmental impact statement for the EPA first? I'm sure they wouldn't be overly pleased... :-) Saen.

5 5

60 Day Termination Notice (fwd)
by Elise Gerich 01 Mar '95

01 Mar '95

Hi, Some of you may receive this twice since it has been sent to the regional-techs list and FARNET, but it seemed important to try to reach as many folks as possible who might be impacted by this. The IBM, MCI, ANS, and Merit partnership during the NSFNET project was a cohesive collaborative effort, and I was really proud to be a part of it. I hope that those of you who continue to provide backbone services have as much fun and success as we did. --Elise > > -------------------------forwarded message-------------------------- > Date: Tue, 28 Feb 95 12:20:00 EST > Message-Id: <9502281720.AA03150(a)pepper.merit.edu> > To: becker(a)ans.net, dstaudt(a)nsf.gov, dvanbell(a)nsf.gov, phustone(a)nsf.gov > Subject: 60 Day Termination Notice > Cc: ema(a)merit.edu, epg(a)merit.edu, ittai(a)ans.net > Status: RO > > Dear Jordan, > It is with mixed feelings that Merit sends this notification > to ANS to terminate the NSFNET Backbone Service at the > following locations: > > ENSS 128 Palo Alto April 30, 1995 midnight PST > ENSS 129 Champaign April 30, 1995 midnight CST > ENSS 130 Argonne April 30, 1995 midnight CST > ENSS 131 Ann Arbor April 30, 1995 midnight EST > ENSS 132 Pittsburgh April 30, 1995 midnight EST > ENSS 133 Ithaca April 30, 1995 midnight EST > ENSS 134 Cambridge April 30, 1995 midnight EST > ENSS 135 San Diego April 30, 1995 midnight PST > ENSS 136 College Park April 30, 1995 midnight EST > ENSS 137 Princeton April 30, 1995, midnight EST > ENSS 139 Houston April 30, 1995, midnight CST > ENSS 140 Lincoln April 30, 1995, midnight CST > ENSS 141 Boulder April 30, 1995, midnight MST > ENSS 142 Salt Lake City April 30, 1995, midnight MST > ENSS 143 Seattle April 30, 1995, midnight PST > ENSS 144 Moffett Field April 30, 1995, midnight PST > ENSS 145 College Park April 30, 1995, midnight EST > ENSS 146 DC April 30, 1995, midnight EST > ENSS 147 MFS April 30, 1995, midnight EST > > This notification also pertains to the cessation of NSFNET > Backbone Service at the Ameritech, MFS, PacBell, and > Sprint Network Access Points. A termination notice was > issued previously for ENSS 138 (Atlanta) so that node > is not included in this termination notice. > > It is sad to note that at midnight in each respective time > zone, the service that Merit, ANS, IBM, and MCI have > collaborated to provide over the last seven years will > cease to exist. It is also with pleasure that we > complete this grand experiment on such a successful > note. I think that this partnership has succeeded > beyond any of our dreams. It has been fun! > > --Elise > -------------------------end of forwarded message----------- >

1 0

Re: 60 Day Termination Notice (fwd)
by swolff＠cisco.com 01 Mar '95

01 Mar '95

>I envisage a fancy-dress gathering in Ann Arbor and D.C. to >party, get blitzed, and then watch as ENSSes get turned off, >and as a big silver ball descends to mark the end of the >NSFNET backbone service... > >BTW, out of curiosity, will the ENSSes get turned off, just >shutdown(8)ed, or have the interfaces ifconfig-ed off? Gee. I hoped each ENSS was gong to get an Ignite packet to /dev/thermite. <sigh> -s

2 1

Re: 60 Day Termination Notice (fwd)
by Sean Doran 01 Mar '95

01 Mar '95

Wow. History in the making. This is better than CNN. I envisage a fancy-dress gathering in Ann Arbor and D.C. to party, get blitzed, and then watch as ENSSes get turned off, and as a big silver ball descends to mark the end of the NSFNET backbone service... BTW, out of curiosity, will the ENSSes get turned off, just shutdown(8)ed, or have the interfaces ifconfig-ed off? Sean. (who is prepared to sing Auld Lang Syne :) )

5 5