exploit the possibilities
Home Files News &[SERVICES_TAB]About Contact Add New

allied-flaw.txt

allied-flaw.txt
Posted Dec 21, 2006
Authored by Pasi Sjoholm

The Allied Telesis AT-9000/24 ethernet switch management has a flaw where it can be accessed from all VLANs.

tags | advisory
SHA-256 | 3791ed7cbd38a884cf82aac7b846aed79ba2a5ea4354ec2a8ecfd524a961988b

allied-flaw.txt

Change Mirror Download
1. Overview

The AT-9000/24 Ethernet switch's management can be accessed
from any VLAN which has been configured to switch.

Normally remote management (SNMP, telnet, http) should be
only available from management VLAN and with AT-9000/24
this can't be chosen. Only option for the management
VLAN is "Default VLAN" (ID 1).

>From User's guide, page 200:
--cut--
The remote management station must be a member of the switch.s
Default VLAN. The switch responds and processes management
packets only if they are received on an untagged port of the Default
VLAN.
--cut--

However when switch is configured to consist more VLANs than
just the "Default VLAN" the management is also available for
all of these VLANs.

This means that the management of the switch is available
for cracking attemps. The cracker only has to get the
information in which subnet (ip-address) the switch
management responds and of course the passwords to
access the management.

For example:

a) SNMP agent has been enabled (not enabled by default)
with the default community passwords in the AT-9000/24 switch.
Port setting can be reset easily after this.
Eg. mirror all the "development-VLAN" packets to a port
in a "DMZ-vlan" which consists a compromised server.
Packets can be captured for later analyzing.

b) Default admin-account "manager" password is left to default
one because admin trusts that the switch only handles the
packets from the "Default VLAN". A unauthorized person
marks the port which he communicating through to another
VLAN as a tagged port. Now the unauthorized person has a
access to another VLAN.

2. Affected Versions

The current "AT-9000/24 Management System Version 1.1.0.06" and prior
are affected.

3. Solution

Software upgrade:
Allied Telesis is working on to fix this bug. However the release
date is unknown.

Workaround:
Unset ip-address for the switch and use only local management through
serial cable.

4. Timeline

The vulnerability was first discovered on 12th December 2006, and was
reported to Allied Telesis support on the same day.

The Allied Telesis development center has confirmed the bug on
14th December 2006.

5. References

AT-S84 User's guide
http://www.alliedtelesyn.com/datasheets/s84_ug_a_v11.pdf

AT-9000/24 Homepage
http://www.alliedtelesyn.com/products/details.aspx?604

--
Pasi Sjöholm
Login or Register to add favorites

File Archive:

April 2024

  • Su
  • Mo
  • Tu
  • We
  • Th
  • Fr
  • Sa
  • 1
    Apr 1st
    10 Files
  • 2
    Apr 2nd
    26 Files
  • 3
    Apr 3rd
    40 Files
  • 4
    Apr 4th
    6 Files
  • 5
    Apr 5th
    26 Files
  • 6
    Apr 6th
    0 Files
  • 7
    Apr 7th
    0 Files
  • 8
    Apr 8th
    22 Files
  • 9
    Apr 9th
    14 Files
  • 10
    Apr 10th
    10 Files
  • 11
    Apr 11th
    13 Files
  • 12
    Apr 12th
    14 Files
  • 13
    Apr 13th
    0 Files
  • 14
    Apr 14th
    0 Files
  • 15
    Apr 15th
    30 Files
  • 16
    Apr 16th
    10 Files
  • 17
    Apr 17th
    22 Files
  • 18
    Apr 18th
    45 Files
  • 19
    Apr 19th
    0 Files
  • 20
    Apr 20th
    0 Files
  • 21
    Apr 21st
    0 Files
  • 22
    Apr 22nd
    0 Files
  • 23
    Apr 23rd
    0 Files
  • 24
    Apr 24th
    0 Files
  • 25
    Apr 25th
    0 Files
  • 26
    Apr 26th
    0 Files
  • 27
    Apr 27th
    0 Files
  • 28
    Apr 28th
    0 Files
  • 29
    Apr 29th
    0 Files
  • 30
    Apr 30th
    0 Files

Top Authors In Last 30 Days

File Tags

Systems

packet storm

© 2022 Packet Storm. All rights reserved.

Services
Security Services
Hosting By
Rokasec
close