SNS Vulnerability

Monkey CMS Multiple Vulnerabilities

Description

Multiple vulnerabilities have been discovered in Monkey CMS, which can be exploited by malicious users to conduct SQL injection attacks and by malicious people to disclose certain system information, conduct SQL injection attacks, and compromise a vulnerable system.
1) The application does not properly restrict access to the admincp/phpinfo.php script, which can be exploited to e.g. disclose PHP and web server configuration.
2) Input passed via the "asstart", "contentelement", "definitionid", "direction", "enddate", "orderby", "perpage", "searchterm", and "startdate" parameters to advancedsearch.php and advancedsearch2.php is not properly sanitised before being used in a SQL query. This can be exploited to manipulate SQL queries by injecting arbitrary SQL code.
3) Input passed via the "searchid" parameter to advancedsearch.php and advancedsearch2.php is not properly sanitised before being used in a SQL query. This can be exploited to manipulate SQL queries by injecting arbitrary SQL code.
4) Input passed via the "User-Agent" HTTP header is not properly sanitised before being used in a SQL query. This can be exploited to manipulate SQL queries by injecting arbitrary SQL code.
5) Input passed via the "tags" GET parameter to index.php (when "page" is set to "TagIndex") is not properly sanitised before being used in an "eval()" call. This can be exploited to execute arbitrary PHP code.
The vulnerabilities are confirmed in version 1.5.19. Other versions may also be affected.

Vulnerable Products

Vulnerable Software:
MonkeyCMS 1.x

Solution

No official solution is currently available.

CVE

References

http://www.exploit-db.com/exploits/26319/

Vulnerability Manager Detection

IPS Protection

ASQ Engine alarm	Available Since
SQL injection Prevention - POST : suspicious SELECT statement in data	3.2.0
SQL injection Prevention - POST : possible version probing in data	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 - POST : suspicious DROP statement in data	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 - POST : suspicious EXEC statement in data	3.2.0
SQL injection Prevention - POST : suspicious OPENROWSET statement in data	3.2.0
SQL injection Prevention - POST : suspicious DECLARE statement in data	3.2.0
SQL injection Prevention - POST : suspicious HAVING statement in data	3.2.0
SQL injection Prevention - POST : suspicious CAST statement in data	3.2.0
SQL injection Prevention - POST : suspicious UPDATE statement in data	5.0.0
SQL injection Prevention - POST : suspicious SELECT statement in data	5.0.0
SQL injection Prevention - POST : suspicious DECLARE statement in data	5.0.0
SQL injection Prevention - POST : suspicious OPENROWSET statement in data	5.0.0
SQL injection Prevention - POST : suspicious OPENQUERY statement in data	5.0.0
SQL injection Prevention - POST : suspicious CAST statement in data	5.0.0
SQL injection Prevention - POST : suspicious EXEC statement in data	5.0.0
SQL injection Prevention - POST : suspicious CREATE statement in data	5.0.0
SQL injection Prevention - POST : suspicious INSERT statement in data	5.0.0
SQL injection Prevention - POST : suspicious DROP statement in data	5.0.0
SQL injection Prevention - POST : suspicious HAVING statement in data	5.0.0
SQL injection Prevention - POST : suspicious UNION statement in data	5.0.0
SQL injection Prevention - POST : suspicious OR statement in data	5.0.0
SQL injection Prevention - POST : possible version probing in data	5.0.0

Risk level

High

Vulnerability First Public Report Date

2013-06-25

Target Type

Server

Possible exploit

Remote