Defending Against Web Spoofing: Creating a Trusted Path from Browser to User in Mozilla Browser

1. Outline • Motivation • Web spoofing problem • Web spoofing attacks – works done • Web spoofing Countermeasures – works done • New Idea

2. Citibank scam - 2004 Your account was blocked , you have to fill a form in the following link email citibank account holder Not the real bank Tricked to the wrong site

3. PayPal Targeted by Scam Artists - 2002 We are replacing the current system with a new one. click here to fill your details. https://www.paypal.com/cgi-bin/webscr/?cmd=_login-run http://www.paypalsys.com/ email account holder Not the real bank Tricked to the wrong site

4. Bank Leumi – potential scam Consistency Lack Complex Url Structure http://www.bll.co.il http://www.leumi.co.il http://www.bankleumi.co.il http://www.leumibank.co.il

5. Our Players user server server authentication is possible. Is the browser-user communication model secure enough to warrant this assumption. performs sensitive tasks.

6. Intended site Faked site Other sites Spoofing is pretending to be someone else. Internet He Wants to check his bank account Great. I get it. Faked Site ! Web Spoofing The user surf a “faked site” as it was the real one he intended to.

7. Faked Site • Site that imitate another one in its appearance and action for malicious purposes. • To succeed , the imitation process must take into account the level of awareness of the potential victim. Content imitation Content & Status imitation • Imitate the page content • Created by copying HTML files. • “fine” for users who judge sites according to their Visual Context. • page content as sent by the server • Status information produced by the browser • Actions must be imitated • Requires some programming efforts. • “fine” for sophisticated users.

8. How the Users Get “Phished” • Normal surfing • Link in popular web page • Search engine • Web-enabled email • Sent by the attacker • Man in the middle attack • The attacker sit between the user and the real site

9. Works Done • Web spoofing: An Internet Con Game -1996 • Edward W.Felten and others. • spoofing entire WWW attacks • Web Spoofing Revisited: SSL and Beyond – 2002 • Zishuang , Yuan and Smith. • Can users believe what their browsers tell them? • Trust on Web Browser: Attack vs. Defence • No author given • Trusted Paths for Browsers: An Open-Source Solution • to Web Spoofing – 2002 • Zishuang , Yuan and Smith. • Demonstrate Open source solution remedy

10. change page 1 request url 4 spoofed page content 5 www.attacker.org • Victim somehow lured into the attacker Web. • Victim remains trapped in the attacker’s web due to url rewriting . Request real url real page content 3 2 http://home.netscape.com rewritten http://www.attacker.org/ http://home.netscape.com 4 www.server.com

11. Complete the Illusion • Still there some evidence that may disclose the attack. • Status Line • Mouse click/move events written in javascript • Location Line • Replace the original with fake one. • Viewing Document Source • Hide the menu bar and provide another • SSL evidence do not help • The secure connection made against the attacker’s site.

12. The target was WebBlitz , a web-based e-mail system. • The language used was Javascript. • They take into account the browser type.(Netscape , IE). • Create new window with all bars turned off . • They provide a interactive fake bars instead. • The location bar get input from keyboard • A fake statusbar with lock icon to indicate SSL session. • The fake statusbar updated as needed • SSL warning windows spoofed also. • They spoof the server certificate that emerged when lock icon double clicked • Images were cached to improve load time

13. Countermeasures • Browser Configuration & recommendations • Configuring browser settings: disable javascript • Short term • Maybe selective • Make sure the location bar always visible • Make sure the url points to the server you intended to • Browser Extension • Extending functionality so the user interface is safe • Long term Good solution must prevent web spoofing and keep the browser in full functionality.

14. Abstract • suggest a solution that defend against web spoofing. • create a trusted path from the browser to the user. • implemented in Mozilla: open source browser. • Design Criteria • Effectiveness • User can correctly recognize large amount of status info • Work • Cannot expect users to do a lot of work • Intrusiveness • Minimize intrusion on content

15. Rejected Approaches • Preventing the open of windows with status elements turned off. • What about pop-up warning window • What about certificate information pages • Constrict the display of server pages • User enter a “MAC phrase” at startup and browser insert it in each status element. • Adding some phrase to the title of windows.

16. Solution • marking scheme that servers could not predict. • This scheme marks the trusted status content. • Synchronized random dynamic boundaries SRD Window Types Style of boundary changes in random. trusted untrusted Server material Browser material

17. Animation of the Solution

18. New Idea • Creating a safe region in the top of each browser window. • It is out of loaded sites control. • Enable personal skinning. • SSL secured sites identified by a logo in this region. • Credential logos will appear in this region • Implemented in Mozilla browser.

19. המלצה אזור בטוח לוגו לזיהוי

20. Ineraction between TBRS and other entities דפדפן משופר דפדפן אתר הקמת ערוץ בטוח / אמות תעודת שרת TBSR רשימת המלצות ולוגויים ע"פ בקשה המלצות נוספות מהאנטרנט

21. TBRS Components אתר נצפה מקורות נוספים ה מ ל צ ו ת CCM CTM המלצות שנאספו תעודת שרת ראשונית דפדפן המלצות במבנה אחיד CAMM מאפיינים ממופים ללוגיים SRCM הצגת לוגויים באזור הבטוח