PMASA-2014-8
Announcement-ID: PMASA-2014-8
Date: 2014-08-17
Summary
Multiple XSS vulnerabilities in browse table, ENUM editor, monitor, query charts and table relations pages
Description
With a crafted database, table or a primary/unique key column name it is possible to trigger an XSS when dropping a row from the table. With a crafted column name it is possible to trigger an XSS in the ENUM editor dialog. With a crafted variable name or a crafted value for unit field it is possible to trigger a self-XSS when adding a new chart in the monitor page. With a crafted value for x-axis label it is possible to trigger a self-XSS in the query chart page. With a crafted relation name it is possible to trigger an XSS in table relations page.
Severity
We consider these vulnerabilities to be non critical.
Mitigation factor
These vulnerabilities can be triggered only by someone who is logged in to phpMyAdmin, as the usual token protection prevents non-logged-in users from accessing the required pages.
Affected Versions
Versions 4.0.x (prior to 4.0.10.2), 4.1.x (prior to 4.1.14.3) and 4.2.x (prior to 4.2.7.1) are affected.
Solution
Upgrade to phpMyAdmin 4.0.10.2 or newer, or 4.1.14.3 or newer, or 4.2.7.1 or newer, or apply the patches listed below.
References
Thanks to Ashutosh Dhundhara for reporting the vulnerability in table relations page.
Assigned CVE IDs: CVE-2014-5273
Patches
The following commits have been made to fix this issue:
- 647c9d12e33a6b64e1c3ff7487f72696bdf2dccb
- 2c45d7caa614afd71dbe3d0f7270f51ce5569614
- cd9f302bf7f91a160fe7080f9a612019ef847f1c
- 90ddeecf60fc029608b972e490b735f3a65ed0cb
- 3ffc967fb60cf2910cc2f571017e977558c67821
The following commits have been made on the 4.0 branch to fix this issue:
- 285ed5b8d3bc9279fe6ed01da8151ed66be9b137
- 0433d463b6c05ea7b1080995414268fe0a449b00
- 3668255202062dd7d60bff70236302084e73fc11
- 03b92aa6e923f2b4a54b298cc0042548ff7ba89b
- 098caf93b63d4928e4df53310222c8727d0be9fe
The following commits have been made on the 4.1 branch to fix this issue:
- 2d394521197f81dce0d9529b2d86ed24760b5b2a
- 1956420ddab0595016ba2b3af89f7f82d39f5afa
- 69f746b7dc09f7b1a18b09de0b5cd71f0bcd0a3d
- bbd20b54864a389c7a0cd2c4d4715f00b81a03e9
- 5519905a2519d9a102b172432448c7e91d5601a6
More information
For further information and in case of questions, please contact the phpMyAdmin security team at security@phpmyadmin.net.