ID CVE-2016-5703
Summary SQL injection vulnerability in libraries/central_columns.lib.php in phpMyAdmin 4.4.x before 4.4.15.7 and 4.6.x before 4.6.3 allows remote attackers to execute arbitrary SQL commands via a crafted database name that is mishandled in a central column query.
References
Vulnerable Configurations
  • openSUSE Leap 42.1
    cpe:2.3:o:opensuse:leap:42.1
  • OpenSUSE 13.1
    cpe:2.3:o:opensuse:opensuse:13.1
  • OpenSUSE 13.2
    cpe:2.3:o:opensuse:opensuse:13.2
  • phpMyAdmin 4.4.0
    cpe:2.3:a:phpmyadmin:phpmyadmin:4.4.0
  • phpMyAdmin 4.4.1
    cpe:2.3:a:phpmyadmin:phpmyadmin:4.4.1
  • phpMyAdmin 4.4.1.1
    cpe:2.3:a:phpmyadmin:phpmyadmin:4.4.1.1
  • phpMYAdmin 4.4.2
    cpe:2.3:a:phpmyadmin:phpmyadmin:4.4.2
  • phpMyAdmin 4.4.3
    cpe:2.3:a:phpmyadmin:phpmyadmin:4.4.3
  • phpMyAdmin 4.4.4
    cpe:2.3:a:phpmyadmin:phpmyadmin:4.4.4
  • phpMyAdmin 4.4.5
    cpe:2.3:a:phpmyadmin:phpmyadmin:4.4.5
  • phpMyAdmin 4.4.6
    cpe:2.3:a:phpmyadmin:phpmyadmin:4.4.6
  • phpMyAdmin 4.4.6.1
    cpe:2.3:a:phpmyadmin:phpmyadmin:4.4.6.1
  • phpMyAdmin 4.4.7
    cpe:2.3:a:phpmyadmin:phpmyadmin:4.4.7
  • phpMyAdmin 4.4.8
    cpe:2.3:a:phpmyadmin:phpmyadmin:4.4.8
  • phpMyAdmin 4.4.9
    cpe:2.3:a:phpmyadmin:phpmyadmin:4.4.9
  • phpMyAdmin 4.4.10
    cpe:2.3:a:phpmyadmin:phpmyadmin:4.4.10
  • phpMyAdmin 4.4.11
    cpe:2.3:a:phpmyadmin:phpmyadmin:4.4.11
  • phpMyAdmin 4.4.12
    cpe:2.3:a:phpmyadmin:phpmyadmin:4.4.12
  • phpMyAdmin 4.4.13
    cpe:2.3:a:phpmyadmin:phpmyadmin:4.4.13
  • phpMyAdmin 4.4.13.1
    cpe:2.3:a:phpmyadmin:phpmyadmin:4.4.13.1
  • phpMYAdmin 4.4.14.1
    cpe:2.3:a:phpmyadmin:phpmyadmin:4.4.14.1
  • phpMYAdmin 4.4.15
    cpe:2.3:a:phpmyadmin:phpmyadmin:4.4.15
  • phpMyAdmin 4.4.15.1
    cpe:2.3:a:phpmyadmin:phpmyadmin:4.4.15.1
  • phpMyAdmin 4.4.15.2
    cpe:2.3:a:phpmyadmin:phpmyadmin:4.4.15.2
  • phpMyAdmin 4.4.15.3
    cpe:2.3:a:phpmyadmin:phpmyadmin:4.4.15.3
  • phpMyAdmin 4.4.15.4
    cpe:2.3:a:phpmyadmin:phpmyadmin:4.4.15.4
  • phpMyAdmin 4.4.15.5
    cpe:2.3:a:phpmyadmin:phpmyadmin:4.4.15.5
  • phpMyAdmin 4.4.15.6
    cpe:2.3:a:phpmyadmin:phpmyadmin:4.4.15.6
  • phpMYAdmin 4.6.0
    cpe:2.3:a:phpmyadmin:phpmyadmin:4.6.0
  • phpMYAdmin 4.6.0 Alpha1
    cpe:2.3:a:phpmyadmin:phpmyadmin:4.6.0:alpha1
  • phpMYAdmin 4.6.0 Rc1
    cpe:2.3:a:phpmyadmin:phpmyadmin:4.6.0:rc1
  • phpMYAdmin 4.6.0 Rc2
    cpe:2.3:a:phpmyadmin:phpmyadmin:4.6.0:rc2
  • phpMYAdmin 4.6.1
    cpe:2.3:a:phpmyadmin:phpmyadmin:4.6.1
  • phpMYAdmin 4.6.2
    cpe:2.3:a:phpmyadmin:phpmyadmin:4.6.2
CVSS
Base: 7.5 (as of 14-07-2016 - 13:03)
Impact:
Exploitability:
CWE CWE-89
CAPEC
  • Command Line Execution through SQL Injection
    An attacker uses standard SQL injection methods to inject data into the command line for execution. This could be done directly through misuse of directives such as MSSQL_xp_cmdshell or indirectly through injection of data into the database that would be interpreted as shell commands. Sometime later, an unscrupulous backend application (or could be part of the functionality of the same application) fetches the injected data stored in the database and uses this data as command line arguments without performing proper validation. The malicious data escapes that data plane by spawning new commands to be executed on the host.
  • Object Relational Mapping Injection
    An attacker leverages a weakness present in the database access layer code generated with an Object Relational Mapping (ORM) tool or a weakness in the way that a developer used a persistence framework to inject his or her own SQL commands to be executed against the underlying database. The attack here is similar to plain SQL injection, except that the application does not use JDBC to directly talk to the database, but instead it uses a data access layer generated by an ORM tool or framework (e.g. Hibernate). While most of the time code generated by an ORM tool contains safe access methods that are immune to SQL injection, sometimes either due to some weakness in the generated code or due to the fact that the developer failed to use the generated access methods properly, SQL injection is still possible.
  • SQL Injection through SOAP Parameter Tampering
    An attacker modifies the parameters of the SOAP message that is sent from the service consumer to the service provider to initiate a SQL injection attack. On the service provider side, the SOAP message is parsed and parameters are not properly validated before being used to access a database in a way that does not use parameter binding, thus enabling the attacker to control the structure of the executed SQL query. This pattern describes a SQL injection attack with the delivery mechanism being a SOAP message.
  • Expanding Control over the Operating System from the Database
    An attacker is able to leverage access gained to the database to read / write data to the file system, compromise the operating system, create a tunnel for accessing the host machine, and use this access to potentially attack other machines on the same network as the database machine. Traditionally SQL injections attacks are viewed as a way to gain unauthorized read access to the data stored in the database, modify the data in the database, delete the data, etc. However, almost every data base management system (DBMS) system includes facilities that if compromised allow an attacker complete access to the file system, operating system, and full access to the host running the database. The attacker can then use this privileged access to launch subsequent attacks. These facilities include dropping into a command shell, creating user defined functions that can call system level libraries present on the host machine, stored procedures, etc.
  • SQL Injection
    This attack exploits target software that constructs SQL statements based on user input. An attacker crafts input strings so that when the target software constructs SQL statements based on the input, the resulting SQL statement performs actions other than those the application intended. SQL Injection results from failure of the application to appropriately validate input. When specially crafted user-controlled input consisting of SQL syntax is used without proper validation as part of SQL queries, it is possible to glean information from the database in ways not envisaged during application design. Depending upon the database and the design of the application, it may also be possible to leverage injection to have the database execute system-related commands of the attackers' choice. SQL Injection enables an attacker to talk directly to the database, thus bypassing the application completely. Successful injection can cause information disclosure as well as ability to add or modify data in the database. In order to successfully inject SQL and retrieve information from a database, an attacker:
  • Blind SQL Injection
    Blind SQL Injection results from an insufficient mitigation for SQL Injection. Although suppressing database error messages are considered best practice, the suppression alone is not sufficient to prevent SQL Injection. Blind SQL Injection is a form of SQL Injection that overcomes the lack of error messages. Without the error messages that facilitate SQL Injection, the attacker constructs input strings that probe the target through simple Boolean SQL expressions. The attacker can determine if the syntax and structure of the injection was successful based on whether the query was executed or not. Applied iteratively, the attacker determines how and where the target is vulnerable to SQL Injection. For example, an attacker may try entering something like "username' AND 1=1; --" in an input field. If the result is the same as when the attacker entered "username" in the field, then the attacker knows that the application is vulnerable to SQL Injection. The attacker can then ask yes/no questions from the database server to extract information from it. For example, the attacker can extract table names from a database using the following types of queries: If the above query executes properly, then the attacker knows that the first character in a table name in the database is a letter between m and z. If it doesn't, then the attacker knows that the character must be between a and l (assuming of course that table names only contain alphabetic characters). By performing a binary search on all character positions, the attacker can determine all table names in the database. Subsequently, the attacker may execute an actual attack and send something like:
Access
VectorComplexityAuthentication
NETWORK LOW NONE
Impact
ConfidentialityIntegrityAvailability
PARTIAL PARTIAL PARTIAL
nessus via4
  • NASL family SuSE Local Security Checks
    NASL id OPENSUSE-2016-804.NASL
    description phpMyAdmin was updated to version 4.4.15.7 to fix eight security issues. These security issues were fixed : - CVE-2016-5701: BBCode injection vulnerability (boo#986154) - CVE-2016-5703: SQL injection attack (boo#986154) - CVE-2016-5705: Multiple XSS vulnerabilities (boo#986154) - CVE-2016-5706: DOS attack (boo#986154) - CVE-2016-5730: Multiple full path disclosure vulnerabilities (boo#986154) - CVE-2016-5731: XSS through FPD (boo#986154) - CVE-2016-5733: Multiple XSS vulnerabilities (boo#986154) - CVE-2016-5739: Referrer leak in transformations (boo#986154) This non-security issues was fixed : - Fix issue Setup script doesn't use input type 'password' in all relevant locations
    last seen 2019-02-21
    modified 2016-10-13
    plugin id 91888
    published 2016-06-29
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=91888
    title openSUSE Security Update : phpMyAdmin (openSUSE-2016-804)
  • NASL family FreeBSD Local Security Checks
    NASL id FREEBSD_PKG_E7028E1D3F9B11E681F96805CA0B3D42.NASL
    description Please reference CVE/URL list for details
    last seen 2018-11-13
    modified 2018-11-10
    plugin id 91939
    published 2016-07-05
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=91939
    title FreeBSD : phpMyAdmin -- multiple vulnerabilities (e7028e1d-3f9b-11e6-81f9-6805ca0b3d42)
  • NASL family SuSE Local Security Checks
    NASL id OPENSUSE-2016-806.NASL
    description This phpMyAdmin update to version 4.4.15.7 fixes the following issues : Issues fixed: Setup script doesn't use input type 'password' in all relevant locations Security issues fixed : - PMASA-2016-17 (CVE-2016-5701, CWE-661) https://www.phpmyadmin.net/security/PMASA-2016-17/ - BBCode injection vulnerability - PMASA-2016-19 (CVE-2016-5703, CWE-661) https://www.phpmyadmin.net/security/PMASA-2016-19/ - SQL injection attack - PMASA-2016-21 (CVE-2016-5705, CWE-661) https://www.phpmyadmin.net/security/PMASA-2016-21/ - Multiple XSS vulnerabilities - PMASA-2016-22 (CVE-2016-5706, CWE-661) https://www.phpmyadmin.net/security/PMASA-2016-22/ - DOS attack - PMASA-2016-23 (CVE-2016-5730, CWE-661) https://www.phpmyadmin.net/security/PMASA-2016-23/ - Multiple full path disclosure vulnerabilities - PMASA-2016-24 (CVE-2016-5731, CWE-661) https://www.phpmyadmin.net/security/PMASA-2016-24/ - XSS through FPD - PMASA-2016-26 (CVE-2016-5733, CWE-661) https://www.phpmyadmin.net/security/PMASA-2016-26/ - Multiple XSS vulnerabilities - PMASA-2016-28 (CVE-2016-5739, CWE-661) https://www.phpmyadmin.net/security/PMASA-2016-28/ - Referrer leak in transformations
    last seen 2019-02-21
    modified 2016-10-13
    plugin id 91889
    published 2016-06-29
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=91889
    title openSUSE Security Update : phpMyAdmin (openSUSE-2016-806)
  • NASL family CGI abuses
    NASL id PHPMYADMIN_4_4_15_7.NASL
    description According to its self-reported version number, the phpMyAdmin application hosted on the remote web server is 4.4.x prior to 4.4.15.7. It is, therefore, affected by the following vulnerabilities: - A flaw exists in the setup/frames/index.inc.php script that allows an unauthenticated, remote attacker to access the program on a non-HTTPS connection and thereby inject arbitrary BBCode against HTTP sessions. (CVE-2016-5701) - A flaw exists in the libraries/central_columns.lib.php script when handling database names due to improper sanitization of user-supplied input. An unauthenticated, remote attacker can exploit this, via a crafted database name, to inject or manipulate SQL queries in the back-end database, resulting in modification or disclosure of arbitrary data. (CVE-2016-5703) - Multiple cross-site scripting (XSS) vulnerabilities exist due to improper validation of user-supplied input before returning it to users. An unauthenticated, remote attacker can exploit these, via specially crafted requests, to execute arbitrary script code or HTML in a a user's browser session. (CVE-2016-5705) - A flaw exists in the js/get_scripts.js.php script when handling a large array in the 'scripts' parameter during the loading of a crafted JavaScript file. An unauthenticated, remote attacker can exploit this to cause a denial of service condition. (CVE-2016-5706) - A information disclosure vulnerability exists in the Example OpenID Authentication and Setup scripts that allows an remote attacker, via multiple vectors, to disclose the application's installation path in an error message. (CVE-2016-5730) - A reflected cross-site scripting (XSS) vulnerability exists in the examples/openid.php script when handling OpenID error messages due to improper validation of input before returning it to users. An unauthenticated, remote attacker can exploit this, via a specially crafted request, to execute arbitrary script code in a user's browser session. (CVE-2016-5731) - Multiple cross-site scripting (XSS) vulnerabilities exist due to improper validation of user-supplied input before returning it to users. An unauthenticated, remote attacker can exploit these, via specially crafted requests, to execute arbitrary script code or HTML in a user's browser session. (CVE-2016-5733) - A flaw exists in the table search and replace feature due to improper sanitization of parameters before passing them to the preg_replace() function. An unauthenticated, remote attacker can exploit this, via a specially crafted string, to execute arbitrary PHP code. (CVE-2016-5734) - An information disclosure vulnerability exists in the libraries/Header.class.php script when handling transformations due to a failure to use the 'no-referer' Content Security Policy (CSP) protection mechanism. An unauthenticated, remote attacker can exploit this, via a specially crafted Transformation, to disclose sensitive authentication token information, which then can be potentially used to facilitate cross-site request forgery (XSRF) attacks. (CVE-2016-5739) Note that Nessus has not attempted to exploit these issues but has instead relied only on the application's self-reported version number.
    last seen 2019-02-21
    modified 2018-07-24
    plugin id 99662
    published 2017-04-25
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=99662
    title phpMyAdmin 4.4.x < 4.4.15.7 Multiple Vulnerabilities (PMASA-2016-17, PMASA-2016-19, PMASA-2016-21 - PMASA-2016-24, PMASA-2016-26 - PMASA-2016-28)
  • NASL family Gentoo Local Security Checks
    NASL id GENTOO_GLSA-201701-32.NASL
    description The remote host is affected by the vulnerability described in GLSA-201701-32 (phpMyAdmin: Multiple vulnerabilities) Multiple vulnerabilities have been discovered in phpMyAdmin. Please review the CVE identifiers referenced below for details. Impact : A authenticated remote attacker could exploit these vulnerabilities to execute arbitrary PHP Code, inject SQL code, or to conduct Cross-Site Scripting attacks. In certain configurations, an unauthenticated remote attacker could cause a Denial of Service condition. Workaround : There is no known workaround at this time.
    last seen 2019-02-21
    modified 2018-06-19
    plugin id 96426
    published 2017-01-12
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=96426
    title GLSA-201701-32 : phpMyAdmin: Multiple vulnerabilities
  • NASL family CGI abuses
    NASL id PHPMYADMIN_4_6_3.NASL
    description According to its self-reported version number, the phpMyAdmin application hosted on the remote web server is 4.6.x prior to 4.6.3. It is, therefore, affected by the following vulnerabilities: - A flaw exists in the setup/frames/index.inc.php script that allows an unauthenticated, remote attacker to access the program on a non-HTTPS connection and thereby inject arbitrary BBCode against HTTP sessions. (CVE-2016-5701) - An unspecified flaw exists, whenever the environment lacks a PHP_SELF value, that allows an unauthenticated, remote attacker to inject arbitrary attributes into browser cookies by using a specially crafted URI. (CVE-2016-5702) - A flaw exists in the libraries/central_columns.lib.php script when handling database names due to improper sanitization of user-supplied input. An unauthenticated, remote attacker can exploit this, via a crafted database name, to inject or manipulate SQL queries in the back-end database, resulting in modification or disclosure of arbitrary data. (CVE-2016-5703) - A cross-site scripting (XSS) vulnerability exists in the templates/table/structure/display_table_stats.phtml script when handling table comments due to improper validation of input before returning it to users. An unauthenticated, remote attacker can exploit this, via a specially crafted request, to execute arbitrary script code in a user's browser session. (CVE-2016-5704) - Multiple cross-site scripting (XSS) vulnerabilities exist due to improper validation of user-supplied input before returning it to users. An unauthenticated, remote attacker can exploit these, via specially crafted requests, to execute arbitrary script code or HTML in a a user's browser session. (CVE-2016-5705) - A flaw exists in the js/get_scripts.js.php script when handling a large array in the 'scripts' parameter during the loading of a crafted JavaScript file. An unauthenticated, remote attacker can exploit this to cause a denial of service condition. (CVE-2016-5706) - A information disclosure vulnerability exists in the Example OpenID Authentication and Setup scripts that allows an remote attacker, via multiple vectors, to disclose the application's installation path in an error message. (CVE-2016-5730) - A reflected cross-site scripting (XSS) vulnerability exists in the examples/openid.php script when handling OpenID error messages due to improper validation of input before returning it to users. An unauthenticated, remote attacker can exploit this, via a specially crafted request, to execute arbitrary script code in a user's browser session. (CVE-2016-5731) - A cross-site scripting (XSS) vulnerability exists in the templates/table/structure/display_partitions.phtml script when handling table parameters due to improper validation of input before returning it to users. An unauthenticated, remote attacker can exploit this, via a specially crafted request, to execute arbitrary script code in a user's browser session. (CVE-2016-5732) - Multiple cross-site scripting (XSS) vulnerabilities exist due to improper validation of user-supplied input before returning it to users. An unauthenticated, remote attacker can exploit these, via specially crafted requests, to execute arbitrary script code or HTML in a user's browser session. (CVE-2016-5733) - A flaw exists in the table search and replace feature due to improper sanitization of parameters before passing them to the preg_replace() function. An unauthenticated, remote attacker can exploit this, via a specially crafted string, to execute arbitrary PHP code. (CVE-2016-5734) - An information disclosure vulnerability exists in the libraries/Header.class.php script when handling transformations due to a failure to use the 'no-referer' Content Security Policy (CSP) protection mechanism. An unauthenticated, remote attacker can exploit this, via a specially crafted Transformation, to disclose sensitive authentication token information, which then can be potentially used to facilitate cross-site request forgery (XSRF) attacks. (CVE-2016-5739) Note that Nessus has not attempted to exploit these issues but has instead relied only on the application's self-reported version number.
    last seen 2019-02-21
    modified 2018-07-24
    plugin id 99663
    published 2017-04-25
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=99663
    title phpMyAdmin 4.6.x < 4.6.3 Multiple Vulnerabilities (PMASA-2016-17 - PMASA-2016-28)
refmap via4
bid 91381
confirm
gentoo GLSA-201701-32
suse
  • openSUSE-SU-2016:1699
  • openSUSE-SU-2016:1700
Last major update 28-11-2016 - 15:28
Published 02-07-2016 - 21:59
Last modified 30-10-2018 - 12:27
Back to Top