what you don't know can hurt you
Home Files News &[SERVICES_TAB]About Contact Add New

AvayaData.txt

AvayaData.txt
Posted Feb 26, 2005
Authored by PAgVac

The Avaya IP Office Phone Manager stores sensitive user data in the Windows Registry.

tags | advisory, registry
systems | windows
SHA-256 | a8ef610343d5e19f8fd31dbe3ee860e5f5b3f1434a04a7af1d434055215974f5

AvayaData.txt

Change Mirror Download


Hello there!

I suspect there is a vulnerability in Avaya IP Office Phone Manager, both light and professional edition. The vulnerability is based on the fact that IP Office Phone Manager stores sensitive data such as username, password and PBX IP address under a key within the Windows Registry:

[HKEY_LOCAL_MACHINE\SOFTWARE\Avaya\IP400\Generic]
"UserName"="Joe Smith"
"Password"=""
"PBXAddress"="10.154.1.60"

The previous example shows how and where the sensitive data is stored in the registry. I've had the opportunity to check this in several hosts of my organization. In all these hosts the password always appears as blank password ("Password"=""). However, I do not know if this is due to the fact that those employees were simply using blank passwords to access the PBX or because the IP Office Phone Manager actually saves the password somewhere else.

The previous information could be accessed by an attacker with local access or remote access (through the "Remote Registry" service) to the Windows registry of a certain host. Administrative privileges would be required, at least if the default configuration is used.

In case the attacker is successful at getting access to the previous Windows registry key, he/she would be able to impersonate an employee simply by using the IP Office Phone Manager software and logging to the PBX with the same username and password. This means that the attacker could do things such as check the victim's voicemails and make phonecalls within the organization under the victim's name.

I have been researching in google and serveral vulnerability DBs to see if this problem was already known but I couldn't find anything on it. This is why I decided to post this vulnerability here in the hope that it is indeed new to the public.

I have been able to check that the usernames and IP addresses found in this registry key are actually real information, meaning that the IP address actually matches the IP address of the PBX within the organization and that the username matches the username used to access the PBX as well. So now I just need someone to help me to find out if the passwords stored in this key are indeed real or simply a "obsfucation technique".

Regards,
pagvac (Adrian Pastor)
Login or Register to add favorites

File Archive:

August 2024

  • Su
  • Mo
  • Tu
  • We
  • Th
  • Fr
  • Sa
  • 1
    Aug 1st
    15 Files
  • 2
    Aug 2nd
    22 Files
  • 3
    Aug 3rd
    0 Files
  • 4
    Aug 4th
    0 Files
  • 5
    Aug 5th
    15 Files
  • 6
    Aug 6th
    11 Files
  • 7
    Aug 7th
    43 Files
  • 8
    Aug 8th
    42 Files
  • 9
    Aug 9th
    36 Files
  • 10
    Aug 10th
    0 Files
  • 11
    Aug 11th
    0 Files
  • 12
    Aug 12th
    0 Files
  • 13
    Aug 13th
    0 Files
  • 14
    Aug 14th
    0 Files
  • 15
    Aug 15th
    0 Files
  • 16
    Aug 16th
    0 Files
  • 17
    Aug 17th
    0 Files
  • 18
    Aug 18th
    0 Files
  • 19
    Aug 19th
    0 Files
  • 20
    Aug 20th
    0 Files
  • 21
    Aug 21st
    0 Files
  • 22
    Aug 22nd
    0 Files
  • 23
    Aug 23rd
    0 Files
  • 24
    Aug 24th
    0 Files
  • 25
    Aug 25th
    0 Files
  • 26
    Aug 26th
    0 Files
  • 27
    Aug 27th
    0 Files
  • 28
    Aug 28th
    0 Files
  • 29
    Aug 29th
    0 Files
  • 30
    Aug 30th
    0 Files
  • 31
    Aug 31st
    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