An issue was discovered in phpMyAdmin before 4.9.0. A vulnerability was found that allows an attacker to trigger a CSRF attack against a phpMyAdmin user. The attacker can trick the user, for instance through a broken <img> tag pointing at the victim's phpMyAdmin database, and the attacker can potentially deliver a payload (such as a specific INSERT or DELETE statement) to the victim.

The remote Ubuntu 16.04 ESM / 18.04 ESM / 20.04 ESM host has a package installed that is affected by multiple vulnerabilities as referenced in the USN-4843-1 advisory.

  - libraries/common.inc.php in phpMyAdmin 4.0.x before 4.0.10.7, 4.1.x before 4.1.14.8, and 4.2.x before     4.2.13.1 allows remote attackers to cause a denial of service (resource consumption) via a long password.
    (CVE-2014-9218)

  - An issue was discovered in phpMyAdmin. A specially crafted database name could be used to run arbitrary     PHP commands through the array export feature. All 4.6.x versions (prior to 4.6.4), 4.4.x versions (prior     to 4.4.15.8), and 4.0.x versions (prior to 4.0.10.17) are affected. (CVE-2016-6609)

  - An issue was discovered in phpMyAdmin. In the user interface preference feature, a user can execute an SQL     injection attack against the account of the control user. All 4.6.x versions (prior to 4.6.4), 4.4.x     versions (prior to 4.4.15.8), and 4.0.x versions (prior to 4.0.10.17) are affected. (CVE-2016-6619)

  - An issue was discovered in phpMyAdmin. An authenticated user can trigger a denial-of-service (DoS) attack     by entering a very long password at the change password dialog. All 4.6.x versions (prior to 4.6.4), 4.4.x     versions (prior to 4.4.15.8), and 4.0.x versions (prior to 4.0.10.17) are affected. (CVE-2016-6630)

  - An issue was discovered in phpMyAdmin. It is possible to bypass AllowRoot restriction     ($cfg['Servers'][$i]['AllowRoot']) and deny rules for username by using Null Byte in the username. All     4.6.x versions (prior to 4.6.5), 4.4.x versions (prior to 4.4.15.9), and 4.0.x versions (prior to     4.0.10.18) are affected. (CVE-2016-9849)

  - An issue was discovered in phpMyAdmin. When the arg_separator is different from its default & value, the     CSRF token was not properly stripped from the return URL of the preference import action. All 4.6.x     versions (prior to 4.6.5), 4.4.x versions (prior to 4.4.15.9), and 4.0.x versions (prior to 4.0.10.18) are     affected. (CVE-2016-9866)

  - An issue was discovered in libraries/common.inc.php in phpMyAdmin 4.0 before 4.0.10.20, 4.4.x, 4.6.x, and     4.7.0 prereleases. The restrictions caused by $cfg['Servers'][$i]['AllowNoPassword'] = false are bypassed     under certain PHP versions (e.g., version 5). This can allow the login of users who have no password set     even if the administrator has set $cfg['Servers'][$i]['AllowNoPassword'] to false (which is also the     default). This occurs because some implementations of the PHP substr function return false when given ''     as the first argument. (CVE-2017-18264)

  - phpMyAdmin 4.0, 4.4, and 4.6 are vulnerable to a DOS weakness in the table editing functionality     (CVE-2017-1000014)

  - phpMyAdmin 4.0, 4.4, and 4.6 are vulnerable to a CSS injection attack through crafted cookie parameters     (CVE-2017-1000015)

  - Cross-site scripting (XSS) vulnerability in db_central_columns.php in phpMyAdmin before 4.7.8 allows     remote authenticated users to inject arbitrary web script or HTML via a crafted URL. (CVE-2018-7260)

  - An issue was discovered in js/designer/move.js in phpMyAdmin before 4.8.2. A Cross-Site Scripting     vulnerability has been found where an attacker can use a crafted database name to trigger an XSS attack     when that database is referenced from the Designer feature. (CVE-2018-12581)

  - An attacker can exploit phpMyAdmin before 4.8.4 to leak the contents of a local file because of an error     in the transformation feature. The attacker must have access to the phpMyAdmin Configuration Storage     tables, although these can easily be created in any database to which the attacker has access. An attacker     must have valid credentials to log in to phpMyAdmin; this vulnerability does not allow an attacker to     circumvent the login system. (CVE-2018-19968)

  - In phpMyAdmin before 4.8.4, an XSS vulnerability was found in the navigation tree, where an attacker can     deliver a payload to a user through a crafted database/table name. (CVE-2018-19970)

  - An issue was discovered in phpMyAdmin before 4.8.5. A vulnerability was reported where a specially crafted     username can be used to trigger a SQL injection attack through the designer feature. (CVE-2019-6798)

  - An issue was discovered in phpMyAdmin before 4.9.0.1. A vulnerability was reported where a specially     crafted database name can be used to trigger an SQL injection attack through the designer feature.
    (CVE-2019-11768)

  - An issue was discovered in phpMyAdmin before 4.9.0. A vulnerability was found that allows an attacker to     trigger a CSRF attack against a phpMyAdmin user. The attacker can trick the user, for instance through a     broken <img> tag pointing at the victim's phpMyAdmin database, and the attacker can potentially deliver a     payload (such as a specific INSERT or DELETE statement) to the victim. (CVE-2019-12616)

  - A CSRF issue in phpMyAdmin 4.9.0.1 allows deletion of any server in the Setup page. (CVE-2019-12922)

  - phpMyAdmin before 4.9.2 does not escape certain Git information, related to     libraries/classes/Display/GitRevision.php and libraries/classes/Footer.php. (CVE-2019-19617)

  - In phpMyAdmin 4 before 4.9.4 and 5 before 5.0.1, SQL injection exists in the user accounts page. A     malicious user could inject custom SQL in place of their own username when creating queries to this page.
    An attacker must have a valid MySQL account to access the server. (CVE-2020-5504)

  - phpMyAdmin before 4.9.6 and 5.x before 5.0.3 allows XSS through the transformation feature via a crafted     link. (CVE-2020-26934)

  - An issue was discovered in SearchController in phpMyAdmin before 4.9.6 and 5.x before 5.0.3. A SQL     injection vulnerability was discovered in how phpMyAdmin processes SQL statements in the search feature.
    An attacker could use this flaw to inject malicious SQL in to a query. (CVE-2020-26935)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The version of phpMyAdmin is affected by a Cross-Site Request Forgery (CSRF) vulnerability in the login form leading to potentially allowing an attacker to perform SQL injection. Note that the scanner has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote Ubuntu 18.04 LTS host has a package installed that is affected by multiple vulnerabilities as referenced in the USN-4639-1 advisory.

  - Cross-site scripting (XSS) vulnerability in db_central_columns.php in phpMyAdmin before 4.7.8 allows     remote authenticated users to inject arbitrary web script or HTML via a crafted URL. (CVE-2018-7260)

  - An attacker can exploit phpMyAdmin before 4.8.4 to leak the contents of a local file because of an error     in the transformation feature. The attacker must have access to the phpMyAdmin Configuration Storage     tables, although these can easily be created in any database to which the attacker has access. An attacker     must have valid credentials to log in to phpMyAdmin; this vulnerability does not allow an attacker to     circumvent the login system. (CVE-2018-19968)

  - In phpMyAdmin before 4.8.4, an XSS vulnerability was found in the navigation tree, where an attacker can     deliver a payload to a user through a crafted database/table name. (CVE-2018-19970)

  - An issue was discovered in phpMyAdmin before 4.8.5. A vulnerability was reported where a specially crafted     username can be used to trigger a SQL injection attack through the designer feature. (CVE-2019-6798)

  - An issue was discovered in phpMyAdmin before 4.8.5. When the AllowArbitraryServer configuration setting is     set to true, with the use of a rogue MySQL server, an attacker can read any file on the server that the     web server's user can access. This is related to the mysql.allow_local_infile PHP configuration, and the     inadvertent ignoring of options(MYSQLI_OPT_LOCAL_INFILE calls. (CVE-2019-6799)

  - An issue was discovered in phpMyAdmin before 4.9.0.1. A vulnerability was reported where a specially     crafted database name can be used to trigger an SQL injection attack through the designer feature.
    (CVE-2019-11768)

  - An issue was discovered in phpMyAdmin before 4.9.0. A vulnerability was found that allows an attacker to     trigger a CSRF attack against a phpMyAdmin user. The attacker can trick the user, for instance through a     broken  tag pointing at the victim's phpMyAdmin database, and the attacker can potentially deliver a     payload (such as a specific INSERT or DELETE statement) to the victim. (CVE-2019-12616)

  - In phpMyAdmin 4 before 4.9.4 and 5 before 5.0.1, SQL injection exists in the user accounts page. A     malicious user could inject custom SQL in place of their own username when creating queries to this page.
    An attacker must have a valid MySQL account to access the server. (CVE-2020-5504)

  - In phpMyAdmin 4.x before 4.9.5 and 5.x before 5.0.2, a SQL injection vulnerability has been discovered     where certain parameters are not properly escaped when generating certain queries for search actions in     libraries/classes/Controllers/Table/TableSearchController.php. An attacker can generate a crafted database     or table name. The attack can be performed if a user attempts certain search operations on the malicious     database or table. (CVE-2020-10802)

  - In phpMyAdmin 4.x before 4.9.5 and 5.x before 5.0.2, a SQL injection vulnerability was discovered where     malicious code could be used to trigger an XSS attack through retrieving and displaying results (in     tbl_get_field.php and libraries/classes/Display/Results.php). The attacker must be able to insert crafted     data into certain database tables, which when retrieved (for instance, through the Browse tab) can trigger     the XSS attack. (CVE-2020-10803)

  - In phpMyAdmin 4.x before 4.9.5 and 5.x before 5.0.2, a SQL injection vulnerability was found in retrieval     of the current username (in libraries/classes/Server/Privileges.php and     libraries/classes/UserPassword.php). A malicious user with access to the server could create a crafted     username, and then trick the victim into performing specific actions with that user account (such as     editing its privileges). (CVE-2020-10804)

  - phpMyAdmin before 4.9.6 and 5.x before 5.0.3 allows XSS through the transformation feature via a crafted     link. (CVE-2020-26934)

  - An issue was discovered in SearchController in phpMyAdmin before 4.9.6 and 5.x before 5.0.3. A SQL     injection vulnerability was discovered in how phpMyAdmin processes SQL statements in the search feature.
    An attacker could use this flaw to inject malicious SQL in to a query. (CVE-2020-26935)

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

This update for phpMyAdmin fixes the following issues :

phpMyAdmin was updated to 4.9.0.1 :

  - 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

  - boo#1137497 / PMASA-2019-4 / CVE-2019-12616 / CWE-661:
    Fixed CSRF vulnerability in login form     https://www.phpmyadmin.net/security/PMASA-2019-4/

  - boo#1137496 / PMASA-2019-3 / CVE-2019-11768 / CWE-661:
    Fixed SQL injection in Designer feature     https://www.phpmyadmin.net/security/PMASA-2019-3/

Multiple security vulnerabilities were fixed in phpmyadmin, a MySQL web administration tool, which prevent possible SQL injection attacks, CSRF, the bypass of user restrictions, information disclosure or denial of service.

For Debian 8 'Jessie', these problems have been fixed in version 4:4.2.12-2+deb8u6.

We recommend that you upgrade your phpmyadmin packages.

NOTE: Tenable Network Security has extracted the preceding description block directly from the DLA security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

The phpMyAdmin development team reports : Summary CSRF vulnerability in login form Description A vulnerability was found that allows an attacker to trigger a CSRF attack against a phpMyAdmin user. The attacker can trick the user, for instance through a broken <img> tag pointing at the victim's phpMyAdmin database, and the attacker can potentially deliver a payload (such as a specific INSERT or DELETE statement) through the victim. Severity We consider this vulnerability to be severe. Mitigation factor Only the 'cookie' auth_type is affected; users can temporary use phpMyAdmin's http authentication as a workaround.

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 a 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 a 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)

Note that Tenable Network Security has extracted the preceding description block directly from the Fedora update system website.
Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

According to its self-reported version number, the phpMyAdmin application hosted on the remote web server is 4.x prior to 4.9.0. It is, therefore, affected by a cross-site request forgery (XSRF) vulnerability. A remote attacker can exploit this by tricking a user into visiting a specially crafted web page, allowing the attacker to disclose sensitive information, impersonate the user's identity, or inject malicious content into the victim's web browser.

Note that Nessus has not attempted to exploit these issues but has instead relied only on the application's self-reported version number.

ID	Name	Product	Family	Severity
183178	Ubuntu 16.04 ESM / 18.04 ESM / 20.04 ESM : phpMyAdmin vulnerabilities (USN-4843-1)	Nessus	Ubuntu Local Security Checks	critical
113297	phpMyAdmin 4.x < 4.9.0 Cross-Site Request Forgery	Web App Scanning	Component Vulnerability	medium
143119	Ubuntu 18.04 LTS : phpMyAdmin vulnerabilities (USN-4639-1)	Nessus	Ubuntu Local Security Checks	critical
126490	openSUSE Security Update : phpMyAdmin (openSUSE-2019-1689)	Nessus	SuSE Local Security Checks	critical
125957	Debian DLA-1821-1 : phpmyadmin security update	Nessus	Debian Local Security Checks	high
125936	FreeBSD : phpMyAdmin -- CSRF vulnerability in login form (a5681027-8e03-11e9-85f4-6805ca0b3d42)	Nessus	FreeBSD Local Security Checks	medium
125907	Fedora 29 : php-phpmyadmin-sql-parser / phpMyAdmin (2019-33649e2e64)	Nessus	Fedora Local Security Checks	critical
125906	Fedora 30 : php-phpmyadmin-sql-parser / phpMyAdmin (2019-13d2ba0aed)	Nessus	Fedora Local Security Checks	critical
125856	phpMyAdmin 4.x < 4.9.0 CSRF vulnerablity (PMASA-2019-4)	Nessus	CGI abuses	medium

Detections

Analytics

CVE-2019-12616

medium

Tenable Plugins

critical

medium

critical

critical

high

medium

critical

critical

medium