An issue was discovered in phpMyAdmin before 4.9.2. A crafted database/table name can be used to trigger a SQL injection attack through the designer feature.

There are packages installed that are affected by a vulnerability referenced in the following CVE:

  - An issue was discovered in phpMyAdmin before 4.9.2. A crafted database/table name can be used to trigger a
    SQL injection attack through the designer feature. (CVE-2019-18622)

There are packages installed that are affected by multiple vulnerabilities referenced in the following CVEs:

  - An issue was discovered in phpMyAdmin before 4.9.2. A crafted database/table name can be used to trigger a
    SQL injection attack through the designer feature. (CVE-2019-18622)

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

The version of phpMyAdmin installed on the remote host does not sanitize the database name parameter inside the Designer feature, leading to exposure to a SQL injection vulnerability. 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 host is affected by the vulnerability described in GLSA-202003-39 (phpMyAdmin: SQL injection)

    PhpMyAdmin was vulnerable to a SQL injection attack through the       designer feature.
  Impact :

    An authenticated remote attacker, by specifying a specially crafted       database/table name, could trigger a SQL injection attack.
  Workaround :

    There is no known workaround at this time.

This update for phpMyAdmin to version 4.9.4 fixes the following issues :

  - CVE-2020-5504: SQL injection in user accounts page     (boo#1160456).

This update for phpMyAdmin fixes the following issues :

phpMyAdmin was updated to 4.9.2 :

  - CVE-2019-18622: SQL injection in Designer feature     (boo#1157614)

  - Fixes for 'Failed to set session cookie' error 

  - Advisor with MySQL 8.0.3 and newer

  - Fix PHP deprecation errors

  - Fix a situation where exporting users after a delete     query could remove users

  - Fix incorrect 'You do not have privileges to manipulate     with the users!' warning

  - Fix copying a database's privileges and several other     problems moving columns with MariaDB

  - Fix for phpMyAdmin not selecting all the values when     using shift-click to select during Export

Upstream announcement :

**phpMyAdmin 4.9.2 is released**

2019-11-22

Welcome to phpMyAdmin 4.9.2, a bugfix release that also contains a security fix.

This security fix is part of an ongoing effort to improve the security of the Designer feature and is designated **PMASA-2019-5**. There is also an improvement for how we sanitize Git version information shown on the home page, thanks to Ali Hubail.

This release includes fixes for many bugs, including :

  - Fixes for the 'Failed to set session cookie' error which     relates to the cookie name. In some cases, data stored     in the cookie (such as the previously-used user account)     may not be loaded from a previous phpMyAdmin cookie the     first time you run version 4.9.2

  - Fix for Advisor with MySQL 8.0.3 and newer

  - Fix PHP deprecation errors

  - Fix a situation where exporting users after a delete     query could remove users

  - Fix incorrect 'You do not have privileges to manipulate     with the users!' warning

  - Fix copying a database's privileges and several other     problems moving columns with MariaDB

  - Fix for phpMyAdmin not selecting all the values when     using shift-click to select during Export

There are many, many more bug fixes thanks to the efforts of our developers and other contributors.

The phpMyAdmin team

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 at least 4.7.7 and prior to 4.9.2. It is, therefore, affected by a SQL injection (SQLi) vulnerability. A remote attacker can exploit this by using a crafted database or table name in the designer feature.

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
422563	SCA: security update for phpmyadmin/phpmyadmin (GHSA-jgjc-332c-8cmc)	Tenable Cloud Security	SCA Checks	critical
422563	SCA: security update for phpmyadmin/phpmyadmin (GHSA-jgjc-332c-8cmc)	Tenable Self-Hosted Container Security	SCA Checks	critical
406401	Alpine: multiple phpmyadmin packages: security update to 4.9.2-r0	Tenable Cloud Security	Alpine Linux Local Security Checks	critical
406401	Alpine: multiple phpmyadmin packages: security update to 4.9.2-r0	Tenable Self-Hosted Container Security	Alpine Linux Local Security Checks	critical
113298	phpMyAdmin 4.7.7 < 4.9.2 SQL Injection	Web App Scanning	Component Vulnerability	critical
134725	GLSA-202003-39 : phpMyAdmin: SQL injection	Nessus	Gentoo Local Security Checks	critical
132917	openSUSE Security Update : phpMyAdmin (openSUSE-2020-56)	Nessus	SuSE Local Security Checks	critical
131542	openSUSE Security Update : phpMyAdmin (openSUSE-2019-2599)	Nessus	SuSE Local Security Checks	critical
131461	Fedora 31 : phpMyAdmin (2019-db68ae1fca)	Nessus	Fedora Local Security Checks	critical
131454	Fedora 30 : phpMyAdmin (2019-8f55b515f1)	Nessus	Fedora Local Security Checks	critical
131319	phpMyAdmin 4.7.7 < 4.9.2 SQLi (PMASA-2019-5)	Nessus	CGI abuses	critical

Detections

Analytics

CVE-2019-18622

critical

Tenable Plugins

critical

critical

critical

critical

critical

critical

critical

critical

critical

critical

critical