Zwei Probleme in php-phpmyadmin-sql-parser
ID: | FEDORA-2019-13d2ba0aed |
Distribution: | Fedora |
Plattformen: | Fedora 30 |
Datum: | Fr, 14. Juni 2019, 07:00 |
Referenzen: | https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11768
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-12616 |
Applikationen: | php-phpmyadmin-sql-parser |
Originalnachricht |
|
-------------------------------------------------------------------------------- Fedora Update Notification FEDORA-2019-13d2ba0aed 2019-06-14 00:53:08.264301 -------------------------------------------------------------------------------- Name : php-phpmyadmin-sql-parser Product : Fedora 30 Version : 4.3.2 Release : 1.fc30 URL : https://github.com/phpmyadmin/sql-parser Summary : A validating SQL lexer and parser with a focus on MySQL dialect Description : A validating SQL lexer and parser with a focus on MySQL dialect. This library was originally developed for phpMyAdmin during the Google Summer of Code 2015. Autoloader: /usr/share/php/PhpMyAdmin/SqlParser/autoload.php -------------------------------------------------------------------------------- Update Information: Upstream announcement: Welcome to **phpMyAdmin 4.9.0.1**, a bugfix release that includes important security fixes. This release fixes two security vulnerabilities: * PMASA-2019-3 is an SQL injection flaw in the Designer feature * PMASA-2019-4 is a CSRF attack that's possible through the 'cookie' login form Upgrading is highly recommended for all users. Using the 'http' auth_type instead of 'cookie' can mitigate the CSRF attack. The solution for the CSRF attack does remove the former functionality to log in directly through URL parameters (as mentioned in FAQ 4.8, such as https://example.com/phpmyadmin/?pma_username=root&password=foo). Such behavior was discouraged and is now removed. Other query parameters work as expected; only pma_username and pma_password have been removed. This release also includes fixes for many bugs, including: - Several issues with SYSTEM VERSIONING tables - Fixed json encode error in export - Fixed JavaScript events not activating on input (sql bookmark issue) - Show Designer combo boxes when adding a constraint - Fix edit view - Fixed invalid default value for bit field - Fix several errors relating to GIS data types - Fixed javascript error PMA_messages is not defined - Fixed import XML data with leading zeros - Fixed php notice, added support for 'DELETE HISTORY' table privilege (MariaDB >= 10.3.4) - Fixed MySQL 8.0.0 issues with GIS display - Fixed "Server charset" in "Database server" tab showing wrong information - Fixed can not copy user on Percona Server 5.7 - Updated sql-parser to version 4.3.2, which fixes several parsing and linting problems There are many, many more bug fixes thanks to the efforts of our developers, Google Summer of Code applicants, and other contributors. The phpMyAdmin team ---- **phpmyadmin/sql-parser version 4.3.2** * Fix redundant whitespaces in build() outputs (#228) * Fix incorrect error on DEFAULT keyword in ALTER operation (#229) * Fix incorrect outputs from Query::getClause (#233) * Add support for reading an SQL file from stdin * Fix for missing tokenize-query in Composer's vendor/bin/ directory * Fix for PHP warnings with an incomplete CASE expression (#241) * Fix for error message with multiple CALL statements (#223) * Recognize the question mark character as a parameter (#242) -------------------------------------------------------------------------------- ChangeLog: * Tue Jun 4 2019 Remi Collet |