phpMyFAQ Remote SQL Injection and File Inclusion Vulnerabilities


Description   Multiple vulnerabilities were identified in phpMyFAQ, which could be exploited by attackers to include arbitrary files and/or conduct SQL injection and cross site scripting attacks.
The first issue is due to input validation errors in the "footer.php" and "header.php" scripts when processing a specially crafted "PMF_CONF[version]" or "PMF_LANG[metaLanguage]" parameter, which may be exploited by attackers to cause arbitrary scripting code to be executed by the user's browser.
The second vulnerability is due to an input validation error in the "password.php" script that does not properly filter a specially crafted "username" variable, which may be exploited by remote users to conduct SQL injection attacks.
The third flaw is due to an input validation error in the "index.php" script when processing a specially crafted "LANGCODE" variable, which could be exploited by attackers to include arbitrary files.
     
Vulnerable Products   Vulnerable Software:
phpMyFAQ version 1.5.1 and prior
     
Solution   Upgrade to phpMyFAQ version 1.5.2 : http://www.phpmyfaq.de/download.php
     
CVE   CVE-2005-3050
CVE-2005-3049
CVE-2005-3048
CVE-2005-3047
CVE-2005-3046
     
References   http://www.phpmyfaq.de/advisory_2005-09-23.php
     
Vulnerability Manager Detection   No
     
IPS Protection  
ASQ Engine alarm Available Since
SQL injection Prevention - GET : suspicious OR statement in URL
3.2.0
SQL injection Prevention - POST : suspicious SELECT statement in data
3.2.0
SQL injection Prevention - GET : suspicious combination of 'OR' or 'AND' statements in URL
3.2.0
SQL injection Prevention - POST : possible version probing in data
3.2.0
SQL injection Prevention - GET : suspicious CREATE statement in URL
3.2.0
SQL injection Prevention - GET : suspicious OPENROWSET statement in URL
3.2.0
SQL injection Prevention - POST : suspicious OPENQUERY statement in data
3.2.0
SQL injection Prevention - POST : suspicious CREATE statement in data
3.2.0
SQL injection Prevention - POST : suspicious UPDATE statement in data
3.2.0
SQL injection Prevention - POST : suspicious UNION statement in data
3.2.0
SQL injection Prevention - GET : suspicious OPENQUERY statement in URL
3.2.0
SQL injection Prevention - GET : suspicious shutdown statement in URL
3.2.0
SQL injection Prevention - GET : suspicious UNION SELECT statement in URL
3.2.0
SQL injection Prevention - POST : suspicious DROP statement in data
3.2.0
SQL injection Prevention - GET : possible database version probing
3.2.0
SQL injection Prevention - POST : suspicious INSERT statement in data
3.2.0
SQL injection Prevention - POST : suspicious OR statement in data
3.2.0
SQL injection Prevention - GET : suspicious UPDATE SET statement in URL
3.2.0
SQL injection Prevention - POST : suspicious EXEC statement in data
3.2.0
SQL injection Prevention - GET : suspicious SELECT statement in URL
3.2.0
SQL injection Prevention - GET : suspicious INSERT statement in URL
3.2.0
SQL injection Prevention - GET : suspicious DROP statement in URL
3.2.0
SQL injection Prevention - POST : suspicious OPENROWSET statement in data
3.2.0
SQL injection Prevention - GET : suspicious EXEC statement in URL
3.2.0
SQL injection Prevention - POST : suspicious HAVING statement in data
3.2.0
     


 
 
 
 
 Risk level 
High 

 Vulnerability First Public Report Date 
2005-09-26 

 Target Type 
Server 

 Possible exploit 
Local & Remote