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)

How to install

sudo dnf upgrade --advisory=FEDORA-2019-13d2ba0aed

This update has been submitted for testing by remi.

a year ago

This update test gating status has been changed to 'waiting'.

a year ago

This update test gating status has been changed to 'ignored'.

a year ago

remi edited this update.

a year ago
User Icon imabug provided feedback a year ago
karma

This update has been pushed to testing.

a year ago

This update has reached 7 days in testing and can be pushed to stable now if the maintainer wishes

a year ago

This update has been submitted for stable by remi.

a year ago

This update has been pushed to stable.

a year ago

Please login to add feedback.

Metadata
Type
security
Severity
high
Karma
1
Signed
Content Type
RPM
Test Gating
Settings
Unstable by Karma
-3
Stable by Karma
3
Dates
submitted
a year ago
in testing
a year ago
in stable
a year ago
modified
a year ago
BZ#1717401 CVE-2019-11768 phpmyadmin: specially crafted database name in the designer feature can be used to trigger an SQL injection attack
0
0
BZ#1717402 CVE-2019-12616 phpmyadmin: broken tag provided by attacker and pointing at the victim's phpMyAdmin database can cause CSRF through the victim
0
0
BZ#1717406 CVE-2019-12616 phpMyAdmin: broken tag provided by attacker and pointing at the victim's phpMyAdmin database can cause CSRF through the victim [fedora-all]
0
0
BZ#1717409 CVE-2019-11768 phpMyAdmin: specially crafted database name in the designer feature can be used to trigger an SQL injection attack [fedora-all]
0
0

Automated Test Results