Multiple XSS in Table operations, Database structure, Trigger and Visualize GIS data pages.
Using a crafted table name, it was possible to produce a XSS : 1) On the Database Structure page, creating a new table with a crafted name 2) On the Database Structure page, using the Empty and Drop links of the crafted table name 3) On the Table Operations page of a crafted table, using the 'Empty the table (TRUNCATE)' and 'Delete the table (DROP)' links 4) On the Triggers page of a database containing tables with a crafted name, when opening the 'Add Trigger' popup 5) When creating a trigger for a table with a crafted name, with an invalid definition. Having crafted data in a database table, it was possible to produce a XSS : 6) When visualizing GIS data, having a crafted label name.
We consider these vulnerabilities to be non critical.
These XSS can only be triggered when a table with a crafted name is already present, or if crafted data is already stored in a database table.
Versions 3.4.x are affected, for issues #1 and #2. Versions 3.5.x are affected, for all issues.
Upgrade to phpMyAdmin 188.8.131.52 or 184.108.40.206 or newer or apply the patches listed below.
Thanks to Emanuel Bronshtein for reporting issues #2, #3 and #4.
Assigned CVE ids: CVE-2012-4345
The following commits have been made to fix this issue:
The following commits have been made on the 3.4 branch to fix this issue:
For further information and in case of questions, please contact the phpMyAdmin team. Our website is phpmyadmin.net.