online marketing
Showing posts with label Phishing. Show all posts
Showing posts with label Phishing. Show all posts

Tuesday, October 11, 2011

Hackers Target Facebook Third Party Applications To Invade Your Online Privacy




Most internet users wouldn't consider their Facebook account to be a real security risk.  For the most part, this is true, as Facebook.com is generally safe in terms of the information it gathers.  However, there's a loophole in Facebook's security that hackers are able to use to potentially access and even alter private information on your profile.
In 2007, Facebook introduced its wildly popular application development program.  This program allows third party developers, both companies and individuals, to create applications.  There are currently just over fourteen thousand Facebook applications including everything from cookbooks to virtual zoos.  While this means there's a diversity of great content available to users, it also means that personal information (which each application has access to) is in a wide variety of hands, and this creates security concerns.
How Applications Access Your Private Information
Every time you choose to add an application, Facebook asks you to confirm that you want to let this program both know who you are and access your information.  It's impossible for anyone to  add any application without agreeing to this set of terms.  Once you click okay, that application can technically access quit a bit of public and private profile information. 
While all of the most private information are kept on Facebook servers and require security authentication, a lot of info is available to applications you add. 
According to Facebook's Developers Terms of Use, this can include
". . . your name, your profile picture, your birthday, your hometown location, your current location, your political views, your activities, your interests, your relationship status, your dating interests, your relationship interests, your summer plans, your Facebook user network affiliations, your education history, your work history, copies of photos in your Facebook Site photo albums, and a list of user IDs mapped to your Facebook friends." 
Not only that, but you don't even have to add an application for it to be able to access your information; they can also learn your info whenever any of your friends add the program.  With all this information available, it's easy to see why many are concerned for their privacy. 
The Threat
For the most part, the danger doesn't come from the application developers themselves, but from hackers who may be able to infiltrate and misuse information collected by applications, especially those written by individual developers instead of companies.    2600, a hacker periodical, published an article detailing how to easily compromise three Facebook apps:  Moods, Superwall and Free Gifts.  These loopholes discussed only allow for minor security breaches, nothing really malicious.  For instance, hackers can change the sender and recipient of Superwall posts and free gifts.  There's even a Youtube video of someone changing another user's mood. Clearly, this is not a top level security threat, yet.  If a loophole exists, though, malicious minds can find a way to exploit it, and it's possible that a serious security risk is en route. 
It's important to note that the problem isn't with Facebook, or even with Applications in general, but with certain applications which don't use safe data practices.  The three applications mentioned earlier are exploitable because they use easily modifiable form sheets to collect data.  Other applications, and all the content published by Facebook itself are safe from hackers.  The real difficulty comes in trying to decipher which applications are safe, and how to make sure that you're not at risk.
What to Do
It's hard to find good solutions to the threat posed by Facebook third party applications.   The first thing to do is to make sure that you don't sign up for applications of questionable background.  Each program developer has a profile on Facebook that you can view to gain information about who they are and how to contact them.  This is the best way to find out what, if any, security protocols they use.  Pick applications that are made by reputable developers, and don't add every application that you're invited to.  Also, be judicious about who you add as a friend.  Remember that applications can access your information if any one of your friends signs up.   The more friends you have, the more applications that have access to your data, and the greater the potential of it falling into the wrong hands. 
Many people feel that the best way to ensure privacy is from the top up.  After all, the most certain way to close hacker back doors is for Facebook to take charge, or hold applications to more stringent security requirements.  At present, Facebook's terms of service clearly state that they are not responsible for the actions of third party developers.  Many users are voicing their concern over this policy, and its ramifications for information security, both to Facebook and the applications that they use.
If you think that you have been the victim of "apps hacking," then you should contact both Facebook and the application developer immediately, to alert them to this potential security flaw.  It's also probably a good idea to avoid that application, and others by the same publisher, as they may pose a continued security risk to your online privacy.
While hackers might be able to access some personal information through Facebook third party applications, being vigilant is the key to staying safe on the internet.

Tuesday, September 13, 2011

Tabnapping Is The Latest Phishing Scheme






Tab Napping: A New Type of Phishing Attack










The web is a generative and wild place. Sometimes I think I missed my calling; being devious is so much fun.
 Too bad my parents brought me up with scruples.Most phishing attacks depend on an original deception. If you detect that you are at the wrong URL, or that something is amiss on a page, the chase is up. You’ve escaped the attackers. In fact, the time that wary people are most wary is exactly when they first navigate to a site.What we don’t expect is that a page we’ve been looking at will change behind our backs, when we aren’t looking. That’ll catch us by surprise.
              
        










How The Attack Works




 1.  A user navigates to your normal looking site.
 2.  You detect when the page has lost its focus and hasn’t been interacted with for a while.



 3.  Replace the favicon with the Gmail favicon, the title with “Gmail: Email from Google”,and the page with a Gmail login look-a  -like.This can all be done with just a little bit of  Javascript that takes place instantly.
 4.  As the user scans their many open tabs, the favicon and title act as a strong visual cu—memory is malleable and moldable and the user will most likely simply think they left a Gmail tab open. When they click back to the fake Gmail tab, they’ll see the standard Gmail login page, assume they’ve been logged out, and provide their credentials to log in. The attack preys on the perceived immutability of tabs.  5.  After the user has entered their login information and you’ve sent it back to your server, you redirect them to Gmail. Because they were never logged out in the first place, it will appear as if the login was successful.Targeted Attacks


There are many ways to potentially improve the efficacy of this attack.
Using my CSS history miner you can detect which site a visitor uses and then attack that site (although this is no longer possible in Firefox betas). For example, you can detect if a visitor is a Facebook user, Citibank user, Twitter user, etc., and then switch the page to the appropriate login screen and favicon on demand.
You can make this attack even more effective by changing the copy: Instead of having just a login screen, you can mention that the session has timed out and the user needs to re-authenticate. This happens often on bank websites, which makes them even more susceptible to this kind of attackEven more deviously, there are various methods to know whether a user is currently logged into a service. These methods range from timing attacks on image loads, to seeing where errors occur when you load an HTML webpage in a script tag*. Once you know what services a user is currently logged in to, the attack becomes even more effective.
  
Attack Vector


Every time you include a third-party script on your page, or a Flash widget, you leave yourself wide open for an evil doer to use your website as a staging ground for this kind of attack. If you are the evil doer, you can have this behavior only occur once in a while, and only if the user uses a targeted service. In other words, it could be hard to detect.
You can also use a cross-site scripting vulnerabilities to force the attack to be performed by other websites. And for browsers that do not support changing the favicon, you can use alocation.assign call to navigate the page to a controlled domain with the correct favicon. As long as the user wasn’t looking at the tab when the refresh occurred (which they won’t be), they’ll have no idea what hit them. Combine this with look-alike Unicode domain names and even the most savvy user will have trouble detecting anything is amiss.
Try it Out


You can try it out on this very website (it works in all major browsers). Click away to another tab for at least five seconds. Flip to another tab. Do whatever. Then come back to this tab.
It’s hard to find, isn’t it? It looks exactly like Gmail. I was lazy and took a screenshot of Gmail which loads slowly. It would be better to recreate the page in HTML.
Update: Many people have reported that the attack doesn’t change the favicon in Chrome. This was due to a bug in Chrome which has been fixed in the version 6.0.408.1. Chrome is fully susceptible to this attack.
You can get the source code here: bgattack.js.


 The Fix


This kind of attack once again shows how important our work is on the Firefox Account Manager to keep our users safe. User names and passwords are not a secure method of doing authentication; it’s time for the browser to take a more active role in being your smart user agent; one that knows who you are and keeps your identity, information, and credentials safe.

 

Emi Crops This Blog is Designed by SAN Bro's
Nufail IK
, Sahad NK and Adil Shereef
Thanks to DASH | © 2011