phpMyAdmin 3.5.x before 3.5.8 and 4.x before 4.0.0-rc3 allows remote authenticated users to execute arbitrary code via a /e\x00 sequence, which is not properly handled before making a preg_replace function call within the "Replace table prefix" feature.

This update of phpMyAdmin fixes several security issues.

  - update to 3.5.8.1 (2013-04-24)

  - [security] Remote code execution (preg_replace),     reported by Janek Vind (see PMASA-2013-2)

  - [security] Locally Saved SQL Dump File Multiple File     Extension Remote Code Execution, reported by Janek Vind     (see PMASA-2013-3)

  - fix for bnc#824301

  - PMASA-2013-2 (CVE-2013-3238)

  - fix for bnc#824302

  - PMASA-2013-3 (CVE-2013-3239)

  - update to 3.5.8 (2013-04-08)

  - sf#3828 MariaDB reported as MySQL

  - sf#3854 Incorrect header for Safari 6.0

  - sf#3705 Attempt to open trigger for edit gives NULL

  - Use HTML5 DOCTYPE

  - [security] Self-XSS on GIS visualisation page, reported     by Janek Vind see PMASA-2013-1

  - sf#3800 Incorrect keyhandler behaviour #2

  - fix for bnc#814678

  - PMASA-2013-1 (CVE-2013-1937)

The remote host is affected by the vulnerability described in GLSA-201311-02 (phpMyAdmin: Multiple vulnerabilities)

    Multiple vulnerabilities have been discovered in phpMyAdmin. Please       review the CVE identifiers referenced below for details.
  Impact :

    A remote authenticated attacker could exploit these vulnerabilities to       execute arbitrary code with the privileges of the process running       phpMyAdmin, inject SQL code, or to conduct Cross-Site Scripting and       Clickjacking attacks.
  Workaround :

    There is no known workaround at this time.

Versions of phpMyAdmin 3.5.x prior to 3.5.8.1, or 4.x prior to 4.0.0-rc3 are affected by multiple vulnerabilities :

 - A flaw exists in 'preg_replace' method as it fails to properly sanitize arguments, which can be used to for arbitrary code execution. (CVE-2013-3238)
 - A security weakness exists in the way that locally saved databases are handled.  It is possible that the 'filename_template' parameter can be used to create a file with double extensions. (CVE-2013-3239)
 - A flaw exists where the 'what' parameter is not correctly validated, allowing for a local file inclusion. This flaw reportedly affects phpMyAdmin 4.x only. (CVE-2013-3240)
 - A flaw exists in the 'export.php' script that allows overwrite of global variables, leading to an unauthorized access vulnerability. This flaw reportedly affects phpMyAdmin 4.x only. (CVE-2013-3241)

phpMyAdmin 3.5.8.1 (2013-04-24) ===============================

  - [security] Remote code execution (preg_replace),     reported by Janek Vind (see PMASA-2013-2)

    - [security] Locally Saved SQL Dump File Multiple File       Extension Remote Code Execution, reported by Janek       Vind (see PMASA-2013-3)

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

Updated phpmyadmin package fixes security vulnerabilities :

In some PHP versions, the preg_replace function can be tricked into executing arbitrary PHP code on the server. This is done by passing a crafted argument as the regular expression, containing a null byte. phpMyAdmin does not correctly sanitize an argument passed to preg_replace when using the Replace table prefix feature, opening the way to this vulnerability (CVE-2013-3238).

phpMyAdmin can be configured to save an export file on the web server, via its SaveDir directive. With this in place, it's possible, either via a crafted filename template or a crafted table name, to save a double extension file like foobar.php.sql. In turn, an Apache webserver on which there is no definition for the MIME type sql (the default) will treat this saved file as a .php script, leading to remote code execution (CVE-2013-3239).

According to its self-identified version number, the phpMyAdmin 3.5.x / 4.0.0 install hosted on the remote web server is earlier than 3.5.8.1 / 4.0.0-rc3 and is, therefore, affected by multiple vulnerabilities:

  - The 'preg_replace' fails to properly sanitize     arguments, which can be used to for arbitrary code     execution. (CVE-2013-3238)

  - A security weakness exists in the way that locally saved     databases are handled.  It is possible that the     'filename_template' parameter can be used to create a     file with double extensions. (CVE-2013-3239)

  - A flaw exists where the 'what' parameter was not     correctly validated, allowing for a local file     inclusion. This flaw reportedly affects phpMyAdmin 4.x     only. (CVE-2013-3240)

  - A flaw exists in the 'export.php' script that allows     overwrite of global variables, leading to an     unauthorized access vulnerability. This flaw reportedly     affects phpMyAdmin 4.x only. (CVE-2013-3241)

The phpMyAdmin development team reports :

In some PHP versions, the preg_replace() function can be tricked into executing arbitrary PHP code on the server. This is done by passing a crafted argument as the regular expression, containing a null byte.
phpMyAdmin does not correctly sanitize an argument passed to preg_replace() when using the 'Replace table prefix' feature, opening the way to this vulnerability..

This vulnerability can be triggered only by someone who logged in to phpMyAdmin, as the usual token protection prevents non-logged-in users to access the required form.

phpMyAdmin can be configured to save an export file on the web server, via its SaveDir directive. With this in place, it's possible, either via a crafted filename template or a crafted table name, to save a double extension file like foobar.php.sql. In turn, an Apache webserver on which there is no definition for the MIME type 'sql' (the default) will treat this saved file as a '.php' script, leading to remote code execution.

This vulnerability can be triggered only by someone who logged in to phpMyAdmin, as the usual token protection prevents non-logged-in users to access the required form. Moreover, the SaveDir directive is empty by default, so a default configuration is not vulnerable. The $cfg['SaveDir'] directive must be configured, and the server must be running Apache with mod_mime to be exploitable.

ID	Name	Product	Family	Severity
75055	openSUSE Security Update : phpMyAdmin (openSUSE-SU-2013:1065-1)	Nessus	SuSE Local Security Checks	medium
70753	GLSA-201311-02 : phpMyAdmin: Multiple vulnerabilities	Nessus	Gentoo Local Security Checks	medium
6933	phpMyAdmin 3.5.x < 3.5.8.1 / 4.x < 4.0.0-rc3 Multiple Vulnerabilities	Nessus Network Monitor	CGI	medium
66366	Fedora 17 : phpMyAdmin-3.5.8.1-1.fc17 (2013-7000)	Nessus	Fedora Local Security Checks	medium
66365	Fedora 18 : phpMyAdmin-3.5.8.1-1.fc18 (2013-6977)	Nessus	Fedora Local Security Checks	medium
66364	Fedora 19 : phpMyAdmin-3.5.8.1-1.fc19 (2013-6928)	Nessus	Fedora Local Security Checks	medium
66313	Mandriva Linux Security Advisory : phpmyadmin (MDVSA-2013:160)	Nessus	Mandriva Local Security Checks	medium
66295	phpMyAdmin 3.5.x < 3.5.8.1 / 4.x < 4.0.0-rc3 Multiple Vulnerabilities (PMASA-2013-2 - PMASA-2013-5	Nessus	CGI abuses	medium
66210	FreeBSD : phpMyAdmin -- Multiple security vulnerabilities (8c8fa44d-ad15-11e2-8cea-6805ca0b3d42)	Nessus	FreeBSD Local Security Checks	medium

Detections

Analytics

CVE-2013-3238

critical

Tenable Plugins

medium

medium

medium

medium

medium

medium

medium

medium

medium