Document Title: =============== Facebook Chartity (TAG) - SQL Injection Vulnerability References (Source): ==================== http://www.vulnerability-lab.com/get_content.php?id=336 Release Date: ============= 2011-12-04 Vulnerability Laboratory ID (VL-ID): ==================================== 336 Common Vulnerability Scoring System: ==================================== 7.5 Product & Service Introduction: =============================== The application is currently included and viewable by all facebook charity users. The service is a not external located application sponsored by the Facebook Chartity (TAG) Development Team. (Copy from the Vendors Homepage: http://www.facebook.com/TAG) Facebook is a social networking service and website launched in February 2004, operated and privately owned by Facebook, Inc. As of July 2011, Facebook has more than 750 million active users. Users may create a personal profile, add other users as friends, and exchange messages, including automatic notifications when they update their profile. Facebook users must register before using the site. Additionally, users may join common-interest user groups, organized by workplace, school or college, or other characteristics. (Copy of the Vendor Website: http://en.wikipedia.org/wiki/Facebook) Abstract Advisory Information: ============================== Vulnerability-Lab researcher discovered a remote SQL Injection vulnerability on the Facebooks Chartity (TAG) application. Vulnerability Disclosure Timeline: ================================== 2011-11-22: Vendor Notification 2011-11-22: Vendor Response/Feedback 2011-11-23: Developer Notification 2011-12-05: Public or Non-Public Disclosure Discovery Status: ================= Published Exploitation Technique: ======================= Remote Severity Level: =============== High Technical Details & Description: ================================ A SQL Injection vulnerability is detected on the Facebooks Charity Contest (TAG) appliccation/service. The vulnerability allows an attacker (remote) to inject/execute own sql statements on the affected fb application dbms. Vulnerable Module(s): [+] Facebooks Chartity (TAG) Vulnerable Param(s)/File(s): [+] INDEX (Charity ConTest) - models/video.php Affected Application: [+] facebook.com/TAG --- SQL Error Logs --- Information: A PHP Error was encountered Severity: Notice Message: Trying to get property of non-object Filename: models/video.php Line Number: 17 - A Database Error Occurred Error Number: 1064 You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\'and s.deleted = 0 and v.deleted = 0 ORDER BY `s`.`id` asc LIMIT 5\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\' at line 5 SELECT `v`.*, `s`.`is_approved`, `s`.`is_winnable`, `s`.`total_votes`, `s`.`total_views`, `s`.`total_comments`, `s`.`is_can_vote` , `s`.`is_can_comment`, `s`.`created`, `s`.`prom_id`, `s`.`user_id`, `s`.`deleted`, `u`.`email`, `u`.`facebook_id`, `u`.`first_name` , `u`.`last_name`, `s`.`round_id` FROM (`submissions` s inner join videos v on s.id = v.submission_id inner join users u on u.id = s.user_id) WHERE `s`.`prom_id` = 23 and s.round_id = and s.deleted = 0 and v.deleted = 0 ORDER BY `s`.`id` asc LIMIT 5 Picture(s): ../1.png Proof of Concept (PoC): ======================= The vulnerability can be exploited by remote attackers. For demonstration or reproduce ... URL: http://www.facebook.com/TAG Path: /TAG/ Module: Charity Contest Example: http://[FACEBOOK]/[SERVICE]/[FILE]?=[SQL Injection] PoC: http://www.facebook.com/TAG?[PARAM]=[SQL-Injection] Solution - Fix & Patch: ======================= Use the prepared statement class to fix the sql injection vulnerability & filter sql error requests. Set error(0) to prevent against information disclosure via exceptions or error reports. Security Risk: ============== The security risk of the application sql injection vulnerabilities are estimated as high(+). Credits & Authors: ================== Vulnerability Research Laboratory - Ucha Gobejishvili (longrifle0x) Disclaimer & Information: ========================= 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: www.vulnerability-lab.com - www.vuln-lab.com - www.vulnerability-lab.com/register Contact: admin@vulnerability-lab.com - support@vulnerability-lab.com - research@vulnerability-lab.com Section: video.vulnerability-lab.com - forum.vulnerability-lab.com - news.vulnerability-lab.com Social: twitter.com/#!/vuln_lab - facebook.com/VulnerabilityLab - youtube.com/user/vulnerability0lab Feeds: vulnerability-lab.com/rss/rss.php - vulnerability-lab.com/rss/rss_upcoming.php - vulnerability-lab.com/rss/rss_news.php 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 (admin@vulnerability-lab.com or support@vulnerability-lab.com) to get a permission. Copyright © 2012 | Vulnerability Laboratory