The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers). An example of a network attack is an attacker causing a denial of service by sending a specially crafted TCP packet across a wide area network (e.g., CVE-2004-0230).
Attack Complexity
Low
AC
The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Privileges Required
Low
PR
The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction
None
UI
The vulnerable system can be exploited without interaction from any human user, other than the attacker. Examples include: a remote attacker is able to send packets to a target system a locally authenticated attacker executes code to elevate privileges
Scope
Unchanged
S
An exploited vulnerability can only affect resources managed by the same security authority. In the case of a vulnerability in a virtualized environment, an exploited vulnerability in one guest instance would not affect neighboring guest instances.
Confidentiality
High
C
There is total information disclosure, resulting in all data on the system being revealed to the attacker, or there is a possibility of the attacker gaining control over confidential data.
Integrity
High
I
There is a total compromise of system integrity. There is a complete loss of system protection, resulting in the attacker being able to modify any file on the target system.
Availability
High
A
There is a total shutdown of the affected resource. The attacker can deny access to the system or data, potentially causing significant loss to the organization.
Title:
======
Facebook Profile Sticker - SQL Injection Vulnerability
Date:
=====
2012-02-03
References:
===========
http://www.vulnerability-lab.com/get_content.php?id=409
VL-ID:
=====
409
Introduction:
=============
The application is currently included and viewable by all facebook users.
The service is an external 3rd party application sponsored by the Facebook Profile Sticker Development Team.
(Copy from the Vendors Homepage: http://apps.facebook.com/myprofilestickers/)
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:
=========
Vulnerability-Lab researcher discovered a remote SQL Injection vulnerability on the 3rd party web
application - Facebook Profile Sticker (apps.facebook.com).
Report-Timeline:
================
2012-02-03:Public or Non-Public Disclosure
Status:
========
Published
Exploitation-Technique:
=======================
Remote
Severity:
=========
High
Details:
========
A remote SQL Injection vulnerability is detected on the Facebook Profile Sticker application (apps.facebook).
The vulnerability allows an attacker (remote) to inject/execute own sql statements on the affected fb application dbms.
Vulnerable Module(s):
[+] Profile Sticker - Facebook 3rd Party Application
Vulnerable Param(s)/File(s):
[+] index.php
Affected Application:
[+] apps.facebook.com/myprofilestickers
--- SQL Error Logs ---
Fatal error: Uncaught exception DbQueryFailure with message 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 -9 , 9 at line 1 SELECT * FROM stickers
where active = 1 and user > 0 order by times_added desc limit -9 , 9 in /var/www/html/profilestickers/lib/classes/Db.php:47
Stack trace: #0 /var/www/html/profilestickers/ajax_scripts/get_stickers.php(69): Db->query( SELECT * FROM s... ) #1
/var/www/html/profilestickers/index.php(297): include_once( /var/www/html/p... ) #2 {main} thrown in /var/www/html
/profilestickers/lib/classes/Db.php on line 47
Picture(s):
../1.png
Proof of Concept:
=================
The vulnerability can be exploited by remote attackers. For demonstration or reproduce ...
URL:http://apps.facebook.com/
Path:/myprofilestickers/
File:index.php
Example:
http://[APP-SERVER]/[SERVICE-APP]/[FILE].[PHP]?[VALUE]=[SQL Injection]
PoC:
http://apps.facebook.com/myprofilestickers/index.php?page=-1'[SQL-Injection]
Risk:
=====
The security risk of the application sql injection vulnerability is estimated as high.
Credits:
========
Vulnerability Research Laboratory - Benjamin Kunz Mejri
Disclaimer:
===========
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. Any modified copy or reproduction, including partially usages, of this file requires authorization from Vulnerability-
Lab. 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 or its suppliers.
Copyright 2012|Vulnerability-Lab
--
Website: www.vulnerability-lab.com ; vuln-lab.com or vuln-db.com
Contact: [email protected] or [email protected]
This information is provided for TESTING and LEGAL RESEARCH purposes only. All trademarks used are properties of their respective owners. By visiting this website you agree to Terms of Use and Privacy Policy and Impressum