FreshPorts - VuXML

This page displays vulnerability information about FreeBSD Ports.

The last vuln.xml file processed by FreshPorts is:

Revision:  374986
Date:      2014-12-20
Time:      00:21:30Z
Committer: delphij

List all Vulnerabilities, by package

List all Vulnerabilities, by date

These are the vulnerabilities relating to the commit you have selected:

VuXML IDDescription
aca0d7e0-e38a-11e1-999b-e0cb4e266481phpMyAdmin -- Path disclosure due to missing library

The phpMyAdmin development team reports:

The show_config_errors.php script does not include a library, so an error message shows the full path of this file, leading to possible further attacks.


Discovery 2012-08-03
Entry 2012-08-11
phpMyAdmin
lt 3.5.2.1

CVE-2012-4219
http://www.phpmyadmin.net/home_page/security/PMASA-2012-3.php
db1d3340-e83b-11e1-999b-e0cb4e266481phpMyAdmin -- Multiple XSS in Table operations, Database structure, Trigger and Visualize GIS data pages

The phpMyAdmin development team reports:

Using a crafted table name, it was possible to produce a XSS : 1) On the Database Structure page, creating a new table with a crafted name 2) On the Database Structure page, using the Empty and Drop links of the crafted table name 3) On the Table Operations page of a crafted table, using the 'Empty the table (TRUNCATE)' and 'Delete the table (DROP)' links 4) On the Triggers page of a database containing tables with a crafted name, when opening the 'Add Trigger' popup 5) When creating a trigger for a table with a crafted name, with an invalid definition. Having crafted data in a database table, it was possible to produce a XSS : 6) When visualizing GIS data, having a crafted label name.


Discovery 2012-08-12
Entry 2012-08-17
phpMyAdmin
lt 3.5.2.2

CVE-2012-4345
http://www.phpmyadmin.net/home_page/security/PMASA-2012-4.php
7280c3f6-a99a-11e2-8cef-6805ca0b3d42phpMyAdmin -- XSS due to unescaped HTML output in GIS visualisation page

The phpMyAdmin development team reports:

When modifying a URL parameter with a crafted value it is possible to trigger an XSS.

These XSS can only be triggered when a valid database is known and when a valid cookie token is used.


Discovery 2013-04-18
Entry 2013-04-20
phpMyAdmin
ge 3.5 lt 3.5.8

CVE-2013-1937
http://www.phpmyadmin.net/home_page/security/PMASA-2013-1.php
17326fd5-fcfb-11e2-9bb9-6805ca0b3d42phpMyAdmin -- clickJacking protection can be bypassed

The phpMyAdmin development team reports:

phpMyAdmin has a number of mechanisms to avoid a clickjacking attack, however these mechanisms either work only in modern browser versions, or can be bypassed.

"We have no solution for 3.5.x, due to the proposed solution requiring JavaScript. We don't want to introduce a dependency to JavaScript in the 3.5.x family."


Discovery 2013-08-04
Entry 2013-08-04
phpMyAdmin
lt 4.0.5

http://www.phpmyadmin.net/home_page/security/PMASA-2013-10.php
ef417da3-1640-11e2-999b-e0cb4e266481phpMyAdmin -- Multiple XSS due to unescaped HTML output in Trigger, Procedure and Event pages and Fetching the version information from a non-SSL site is vulnerable to a MITM attack

The phpMyAdmin development team reports:

When creating/modifying a trigger, event or procedure with a crafted name, it is possible to trigger an XSS.

To display information about the current phpMyAdmin version on the main page, a piece of JavaScript is fetched from the phpmyadmin.net website in non-SSL mode. A man-in-the-middle could modify this script on the wire to cause mischief.


Discovery 2012-10-08
Entry 2012-10-14
phpMyAdmin
ge 3.5 lt 3.5.3

CVE-2012-5339
http://www.phpmyadmin.net/home_page/security/PMASA-2012-6.php
CVE-2012-5368
http://www.phpmyadmin.net/home_page/security/PMASA-2012-7.php
8c8fa44d-ad15-11e2-8cea-6805ca0b3d42phpMyAdmin -- Multiple security vulnerabilities

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.


Discovery 2013-04-24
Entry 2013-04-24
phpMyAdmin
ge 3.5 lt 3.5.8.1

CVE-2013-3238
CVE-2013-3239