HP3000-L Archives

October 1996, Week 5

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Mike Hornsby <[log in to unmask]>
Reply To:
Mike Hornsby <[log in to unmask]>
Date:
Wed, 30 Oct 1996 09:01:27 -0600
Content-Type:
text/plain
Parts/Attachments:
text/plain (23 lines)
This ping problem should be viewed  by HP as a very serious security issue.
It basically allows anyone who can reach the HP 3000 or 9000 via TCP IP to
crash them at will. Many other vendors systems and devices are also
vulnerable.

A firewall will only protect the inside network from the outside network.
Sites with remote access servers should be especially concerned because any
dial up user becomes a potential threat.

HP should at least make an effort to identify all vulnerable systems and
devices and warn their customers immediately.  Patches and firmware fixes
should be given a high priority.

How to test if a system, router, or printer is vulnerable:
 (WARNING THIS WILL RESULT IN A SYSTEM ABORT ON AN HP3000!)

Ping -l 65510 ip-address

the -l is the send buffer size

The system abort comes from a bug in the operating system when a 16 bit
offset value overflows.

ATOM RSS1 RSS2