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

hitachiVOIP.txt

hitachiVOIP.txt
Posted Nov 20, 2005
Authored by Shawn Merdinger

Hitachi IP5000 VoIP Wifi phones suffer from multiple vulnerabilities including a hard coded administrator password, an undocumented shell on tcp/3390, and management of the devices without proper credentials.

tags | advisory, shell, tcp, vulnerability
SHA-256 | 3fc76b0a8c041d6233c0d5ce2c8893ad965a07c24340c8183fa546480d2e1c69

hitachiVOIP.txt

Change Mirror Download
I disclosed today the following vulnerabilities at the 32nd CSI
conference in Washington, D.C.
<https://www.cmpevents.com/CSI32/a.asp?option=G&V=3&id=406438>

Thanks,
Shawn Merdinger

===============================================================
VENDOR:
Hitachi

PRODUCT:
Hitachi IP5000 VOIP WIFI Phone
https://www.wirelessip5000.com/

SOFTWARE VERSION:
v1.5.6

VENDOR NOTIFIED:
28 June, 2005

VENDOR RESPONSE:
None. However, issues addressed at
https://www.hitachi-cable.co.jp/ICSFiles/infosystem/security/76659792_e.pdf

A. VULNERABILITY TITLE:
Hitachi IP5000 VOIP WIFI Phone handset hardcoded administrator password

VULNERABILITY DETAILS, IMPACT AND WORKAROUND:
1. The Hitachi VOIP WIFI phone handset has a default administrator
password of "0000" that the user enters in order to access
administrator functions when
programming the handset via the physical keys. This password appears to be
hardcoded and presents a physical vulnerability. If an attacker can physically
access the phone (borrow, phone rental scenario, theft, etc.) the attacker can
derive sensitive information and modify the phone's configuration. There
appears to be no workaround for this vulnerability.

B. VULNERABILITY TITLE:
Hitachi IP5000 VOIP WIFI phone HTTP server vulnerabilities

VULNERABILITY DETAILS, IMPACT AND WORKAROUND:
The HTTP server (port TCP/8080) on the Hitachi IP5000 phone has two security
issues:

1. Improper information disclosure: The HTTP daemon default index page
discloses what the device is (Hitachi IP5000 phone), the phone software
versions, phone MAC address, IP address and routing information. An
attacker can use this to discover quickly what the device is and see if there
are any associated vulnerabilities. Also, the disclosure of the phone's
routing/gateway information can provide an attacker with information for a
DoS attack. An attacker does not need to authenticate to the phone to obtain
this information from the index page. Workaround is to disable the HTTP
server via the phone's physical interface or via the HTTP interface.

2. Web server default configuration does not require credentials to
authenticate.
This allows an attacker to access any of the various configuration pages of the
phone, changing the phone configuration, etc. Workaround is to disable the
HTTP server via the phone's physical interface or via the HTTP interface. The
phone user may also set a password via the HTTP interface. Note that the
password set page does not require the previous password (an attacker could
lock out a user if the initial password is not set), nor does it require the new
password to be entered twice (to avoid fat-fingering).

C. VULNERABILITY TITLE:
Hitachi IP5000 VOIP WIFI Phone SNMP daemon vulnerabilities

VULNERABILITY DETAILS, IMPACT AND WORKAROUND:

1. The Hitachi IP5000 VOIP WIFI phone SNMP v1/v2c daemon allows
read/write access to the phone's SNMP configuration using any credentials. An
attacker can use this vulnerability to access the phone's SNMP configuration,
potentially reading/writing/erasing sensitive information. There seems to be no
workaround as it appears that the SNMP daemon can neither be disabled, nor
can the SNMP daemon read/write strings be modified by the phone user.

D. VULNERABILITY TITLE:
Hitachi IP5000 VOIP WIFI Phone undocumented port TCP/3390 Unidata Shell

VULNERABILITY DETAILS, IMPACT AND WORKAROUND:

1. The Hitachi IP5000 phone has a undocumented open port, TCP/3390, that
provides an unauthenticated attacker access to the Unidata Shell created upon
connection. This may allow an attacker to access sensitive information and
potentially impact the phone's operations in a DoS. As a workaround, there
appears to be no means to disable this port and service, so no workaroud
appears possible.
Login or Register to add favorites

File Archive:

November 2024

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

Top Authors In Last 30 Days

File Tags

Systems

packet storm

© 2024 Packet Storm. All rights reserved.

Services
Security Services
Hosting By
Rokasec
close