[NEWS] Ascend's Undocumented Protocol Allows Unauthorized Modifications

From: support@securiteam.com
Date: 07/28/02


From: support@securiteam.com
To: list@securiteam.com
Date: Sun, 28 Jul 2002 08:14:22 +0200 (CEST)

The following security advisory is sent to the securiteam mailing list, and can be found at the SecuriTeam web site: http://www.securiteam.com
- - promotion

When was the last time you checked your server's security?
How about a monthly report?
http://www.AutomatedScanning.com - Know that you're safe.
- - - - - - - - -

  Ascend's Undocumented Protocol Allows Unauthorized Modifications
------------------------------------------------------------------------

SUMMARY

The product line formerly known under the name of "Ascend" running the
TAOS Operating System provides an easy to use and support interface. This
interface includes an undocumented protocol that provides an easy method
to identify and query the devices (similar to the Cisco CDP problem but
remote).

DETAILS

Vulnerable systems:
 * Pipline, MAX, DSL-Terminator. (Formerly known under Ascend Router
product line

Immune systems:
 * MAX TNT

By sending a crafted UDP packet to the devices UDP discard port (9), the
device will answer with a packet containing valuable information such as
the host's name, MAC, IP address of the Ethernet Interface, Serial number,
device type and installed features. By sending a packet with the SNMP
WRITE community, a remote attacker can change the devices IP address,
netmask or name.

Vendor status:
06/28/02 Reply to inquiry regarding "who to notify"
06/29/02 Initial Notification *Note-Initial notification by phenoelit
includes a cc to cert@cert.org by default
06/29/02 Human response acknowledges the receipt.
07/06/02 Weekly Follow-up by central POC at Lucent
07/08/02 Additional technical discussions
07/19/02 Notification of intent to post publicly in approximately 7 days.

Example:
linux# irpas/dfkaa 192.168.1.11
DFKAA - Devices Formerly Known as Ascend FX <fx@phenoelit.de> -
http://www.phenoelit.de/
$Revision: 1.22 $ - IRPAS Build XL (c) 2001++

>>ascend<<
        [Probe response]
        ADP version: 2
        *MAC addr: 00:C0:7B:89:DD:86
        IP addr: 192.168.1.11/255.255.255.0
        *Serial number: 9990826374
        Device type: Ascend Pipeline 75
        Features: 0004 0030 0140 0000
*Device Serial number and MAC have been changed.

ADDITIONAL INFORMATION

The information has been provided by <mailto:fx@phenoelit.de> FX and
<mailto:kim0@phenoelit.de> kim0.

========================================

This bulletin is sent to members of the SecuriTeam mailing list.
To unsubscribe from the list, send mail with an empty subject line and body to: list-unsubscribe@securiteam.com
In order to subscribe to the mailing list, simply forward this email to: list-subscribe@securiteam.com

====================
====================

DISCLAIMER:
The information in this bulletin is provided "AS IS" without warranty of any kind.
In no event shall we be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages.



Relevant Pages

  • RE: Intrusion Prevention requirements document
    ... The tools consider one interface as "client" and other ... Packet 1 is first sent out on client interface. ... > my previous company was Blade Software where I developed IDS Informer ... Up to 75% of cyber attacks are launched on shopping carts, ...
    (Pen-Test)
  • Re: Pix 515 VLAN NAT0 issues
    ... that ACL will be exempt from NAT. ... the packet at the time the PIX receives the packet. ... ACL applied to an inside interface would have the internal IPs as ... accepted as having a translation and satisfying the security policies. ...
    (comp.dcom.sys.cisco)
  • Re: [RFC] 0/11 fanotify: fscking all notifiction and file access system (intended for antivirus scan
    ... deals with races and exclusion. ... notification file open have very minimal performance hit. ... Ok that is foul as an interface, ... can't use the socket based notification model - that gives you a much ...
    (Linux-Kernel)
  • Re: ipv4 regression in 2.6.31 ?
    ... interface eth1 on host B and let host A ping 192.168.2.1 you get no reply. ... - Strict mode as defined in RFC3704 Strict Reverse Path ... Each incoming packet is tested against the FIB and if the interface ... then loose mode is recommended. ...
    (Linux-Kernel)
  • RE: Intrusion Prevention requirements document
    ... The tools consider one interface as "client" and other ... Packet 1 is first sent out on client interface. ... > The product uses two network cards and so the library of over 700 ... > my previous company was Blade Software where I developed IDS Informer ...
    (Focus-IDS)