bugtraq - phpMyAdmin: reply to vulnerability report (2003-06-18)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <3F02AAF8.3060403@CollegeSherbrooke.qc.ca>
Date: Wed, 02 Jul 2003 05:50:48 -0400
From: Marc Delisle <DelislMa@...legeSherbrooke.qc.ca>
To: bugtraq@...urityfocus.com
Subject: phpMyAdmin: reply to vulnerability report (2003-06-18)


( From http://www.phpmyadmin.net/documentation#faqsecurity )

  Last update: 2003-07-02.

The phpMyAdmin development team received notice of this security alert: 
http://www.securityfocus.com/archive/1/325641.

The team regrets that the author did not communicate with us before 
sending this alert. However, here is our current reply to the points 
mentionned:

     * "Directory transversal attack"

       This problem had been fixed in version 2.5.0, even if the author 
reports the 2.5.2 development version as vulnerable, which we could not 
reproduce.

     * "Remote local file retrieving"

       This is a misleading title, as the author tells in his text: 
"Note that you can't request files ( only dirs )".

     * "Remote internal directory listing"

       It was possible to retrieve the list of phpMyAdmin's directory 
(which we doubt can cause any damage), but we fixed this in the upcoming 
2.5.2 version.

     * "XSS and Path disclosures"

       Most of the XSS problems have been fixed in version 2.5.0. The 
rest have been fixed in the upcoming 2.5.2 version.

       We are currently looking at the Path disclosure issue.

     * "Information encoding weakness"

       We believe that an exploit for this weakness would be difficult 
to achieve. However version 2.5.2-dev now encrypts the password with the 
well-known blowfish algorithm.
-------------

Marc Delisle, for the team.