CUSRF | It's Pronounced "See You Surf" and It's Dangerous
 

CUSRF | It's Pronounced "See You Surf" and It's Dangerous

on

  • 975 views

Cross USer Request Forgery (CUSRF: pronounced "See You Surf") is a new and emerging type of Cross-Site Request Forgery (CSRF) attack that affects users of collaboration platforms and applications, ...

Cross USer Request Forgery (CUSRF: pronounced "See You Surf") is a new and emerging type of Cross-Site Request Forgery (CSRF) attack that affects users of collaboration platforms and applications, such as LinkedIn and Google Docs.

CUSRF exploits vulnerabilities in social networks to reveal a victim's true identity. Due to special technical characteristics of CUSRF attacks, most traditional counter-measures are irrelevant to the attack's mitigation. This presentation will:
- Give a brief intro of CSRF
- Examine the anatomy of a CUSRF attack, with examples
- Discuss mitigation techniques for both consumers and platform providers

Statistics

Views

Total Views
975
Views on SlideShare
974
Embed Views
1

Actions

Likes
1
Downloads
32
Comments
0

1 Embed 1

https://www.linkedin.com 1

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

CUSRF | It's Pronounced "See You Surf" and It's Dangerous CUSRF | It's Pronounced "See You Surf" and It's Dangerous Presentation Transcript

  • © 2014 Imperva, Inc. All rights reserved. CUSRF | It’s Pronounced “See You Surf” and It’s Dangerous Amichai Shulman, CTO, Imperva 1
  • © 2014 Imperva, Inc. All rights reserved. Agenda 2 §  CSRF brief intro §  CUSRF: A close encounter with CSRF of the third kind §  CUSRF explained §  Vulnerable applications in the wild §  Google Docs §  Linkedin.com §  Mitigations §  Summary and conclusion
  • © 2014 Imperva, Inc. All rights reserved. Amichai Shulman – CTO, Imperva 3 §  Speaker at Industry Events •  RSA, Appsec, Info Security UK, Black Hat §  Lecturer on Information Security •  Technion - Israel Institute of Technology §  Former security consultant to banks & financial services firms §  Leads the Application Defense Center (ADC) •  Discovered over 20 commercial application vulnerabilities §  Credited by Oracle, MS-SQL, IBM and others One of InfoWorld’s “Top 25 CTOs”
  • © 2014 Imperva, Inc. All rights reserved. The Motivation: Protecting Your ID in a Hostile Online Environment 4
  • © 2014 Imperva, Inc. All rights reserved. Privacy on the Web: An Uphill Battle? 5 Source: www.askingsmarterquestions.com
  • © 2014 Imperva, Inc. All rights reserved. Privacy Can Be Achieved Through Anonymity 6 Source: www.antiquaprintgallery.com
  • © 2014 Imperva, Inc. All rights reserved. Privacy Can Be Achieved Through Anonymity 7 Source: www.antiquaprintgallery.com
  • © 2014 Imperva, Inc. All rights reserved. CUSRF Vulnerability Opens Your Social Kimono! §  CUSRF (pronounced “See You Surf”) •  Cross USer Request Forgery §  Web sites you visit can see your privates: •  In real-time •  Name, email, work place, title, etc. §  Potential outcomes: •  “Ice Hole Phishing”: e.g. infect only certain roles in a specific organization. •  Display different price •  Disinformation 8
  • © 2014 Imperva, Inc. All rights reserved. CSRF Intro 9
  • © 2014 Imperva, Inc. All rights reserved. SOP Threat Model Communication Custom Code Accounts Finance Administration Transactions KnowledgeMgmt E-Commerce Bus.Functions Target Application Attacker sets the trap on some website on the internet1 Some interaction with victim site 10
  • © 2014 Imperva, Inc. All rights reserved. SOP Threat Model Communication Custom Code Accounts Finance Administration Transactions KnowledgeMgmt E-Commerce Bus.Functions Target Application Attacker sets the trap on some website on the internet1 2 While logged into vulnerable site, victim views attacker site Target site interaction Some interaction with victim site 11
  • © 2014 Imperva, Inc. All rights reserved. SOP Threat Model Communication Custom Code Accounts Finance Administration Transactions KnowledgeMgmt E-Commerce Bus.Functions Target Application 3 Vulnerable site sees legitimate request from victim, performs the requested action and sends a response Attacker sets the trap on some website on the internet1 2 While logged into vulnerable site, victim views attacker site Target site interaction Some interaction with victim site 12
  • © 2014 Imperva, Inc. All rights reserved. CSRF Illustrated: “Bypassing SOP” Attacker sets the trap on some website on the internet (or simply via an e-mail) 1 Custom Code Accounts Finance Administration Transactions Communication KnowledgeMgmt E-Commerce Bus.Functions Hidden <img> tag contains attack against vulnerable site Application with CSRF vulnerability 13
  • © 2014 Imperva, Inc. All rights reserved. CSRF Illustrated: “Bypassing SOP” Attacker sets the trap on some website on the internet (or simply via an e-mail) 1 Hidden <img> tag contains attack against vulnerable site 2 While logged into vulnerable site, victim views attacker site <img> tag loaded by browser – sends GET request (including credentials) to vulnerable site 14
  • © 2014 Imperva, Inc. All rights reserved. CSRF Illustrated: “Bypassing SOP” 3 Attacker sets the trap on some website on the internet (or simply via an e-mail) 1 Vulnerable site sees legitimate request from victim and performs the requested action Custom Code Accounts Finance Administration Transactions Communication KnowledgeMgmt E-Commerce Bus.Functions Hidden <img> tag contains attack against vulnerable site Application with CSRF vulnerability 2 While logged into vulnerable site, victim views attacker site <img> tag loaded by browser – sends GET request (including credentials) to vulnerable site 15
  • © 2014 Imperva, Inc. All rights reserved. CSRF §  The “Confused Deputy” Problem •  Web browsers automatically include access tokens with each request •  Requests can be invoked by malicious sites from victim’s browser without user consent §  Automatically Provided Tokens: Session cookie, basic authentication header, IP address, client side SSL certificates, Windows domain authentication 16
  • © 2014 Imperva, Inc. All rights reserved. CSRF Type I: Classic CSRF 17 §  The “Transfer Fund” attack §  Attacker tricks the browser into issuing a “transfer funds” request to the attacker’s account §  “/transferFund.jsp?To=<attacker>&Sum=10000000” Attack Type Used credentials Interacts with Classic CSRF Victim’s Victim’s web account
  • © 2014 Imperva, Inc. All rights reserved. CSRF Type II: Login CSRF §  The attacker mounts a CSRF attack that logs the victim into an attacker controlled account (sink account) §  “signin.jsp?user=<attacker>&password=123456” §  Later on, the attacker is able to track the victim’s activity in the sink account §  e.g. log the victim to attacker’s controlled Google account to collect search history 18
  • © 2014 Imperva, Inc. All rights reserved. CSRF Type II: Login CSRF §  The attacker mounts a CSRF attack that logs the victim into an attacker controlled account (sink account) §  “signin.jsp?user=<attacker>&password=123456” §  Later on, the attacker is able to track the victim’s activity in the sink account §  e.g. log the victim to attacker’s controlled Google account to collect search history Attack Type Used credentials Interacts with Classic CSRF Victim’s Victim’s web account Login CSRF Attacker’s Attacker web account 19
  • © 2014 Imperva, Inc. All rights reserved. CSRF Type II: Login CSRF §  The attacker mounts a CSRF attack that logs the victim into an attacker controlled account (sink account) §  “signin.jsp?user=<attacker>&password=123456” §  Later on, the attacker is able to track the victim’s activity in the sink account §  e.g. log the victim to attacker’s controlled Google account to collect search history 20
  • © 2014 Imperva, Inc. All rights reserved. CSRF is Very Relevant Source: WhiteHat Security 21
  • © 2014 Imperva, Inc. All rights reserved. CSRF is Very Relevant Source: WhiteHat Security 22
  • © 2014 Imperva, Inc. All rights reserved. CUSRF: A Close Encounter With CSRF of the Third Kind 23
  • © 2014 Imperva, Inc. All rights reserved. CSRF Type III: CUSRF 24 §  A new type of CSRF, bringing CSRF to Web 2.0 environment §  “Cross USer Request Forgery” (CUSRF, pronounced “See You Surf”) attack §  Composition of the known CSRF vulnerability types, for collaboration environment
  • © 2014 Imperva, Inc. All rights reserved. Web 2.0: It’s All About Collaboration 25 §  “A Web 2.0 site may allow users to interact and collaborate with each other in a social media dialogue as creators of user-generated content in a virtual community” (Source: Wikipedia) Source: http://conceptart.ca
  • © 2014 Imperva, Inc. All rights reserved. CUSRF Explained 26 §  The attacker forges collaboration requests on behalf of the victim •  Similar to the “Classic CSRF” §  The collaboration target is located on an attacker controlled account •  Similar to the “Login CSRF” §  Outcome: Attacker can reveal the victim’s social network identity Attack Type Used credentials Interacts with Classic CSRF Victim’s Victim’s web account Login CSRF Attacker’s Attacker’s web account CUSRF Victim’s Attacker’s web account
  • © 2014 Imperva, Inc. All rights reserved. CUSRF in the Wild 1: LinkedIn Profile 27
  • © 2014 Imperva, Inc. All rights reserved. Attack Setup: Creating a LinkedIn Profile 28 §  Attacker sets up a LinkedIn account
  • © 2014 Imperva, Inc. All rights reserved. Attack Setup: Settings 29 §  In order to view the identity of profile visitors, the attacker can either: •  Go “Pro” •  Make their “LinkedIn” identity available to others
  • © 2014 Imperva, Inc. All rights reserved. Attack Setup: CSRF Page 30 §  Attacker adds an invisible CSRF link referencing the attacker’s LinkedIn profile to their online asset §  Asset can be: •  A “watering hole” page •  A “phishing” page •  Etc.
  • © 2014 Imperva, Inc. All rights reserved. Launching the Attack 31 §  When the intended target visits the CSRF page: •  The attacker discovers his identity (“Tal Be’ery”) instantly §  Can act accordingly: •  e.g. infect him personally with a “drive by download“ infection
  • © 2014 Imperva, Inc. All rights reserved. Resolving “Semi Anonymous Profiles” 32 §  Victim can choose to share only “profile characteristics” •  e.g “Engineer in Imperva” §  This is the default setting §  Sometimes that’s enough information for the attacker
  • © 2014 Imperva, Inc. All rights reserved. Resolving “Semi Anonymous Profiles” 33 §  In 2013, Linkedininsights.com had demonstrated a bypass §  Linkedin “Red Herring” Module showed list of 10 possible “candidates” for the “Semi Anonymous Profiles” §  One was the actual person; others were just “Red Herrings” §  The problem: “Red Herrings” were randomized, actual person was not §  Exploit: Attacker should view the “candidates” list twice and mark the overlapping item
  • © 2014 Imperva, Inc. All rights reserved. A Smelly Red Herring 34 Source: www.linkedinsights.com
  • © 2014 Imperva, Inc. All rights reserved. CUSRF in the Wild 2: Google Docs 35
  • © 2014 Imperva, Inc. All rights reserved. Attack Setup: Creating a Google Doc 36 §  Attacker (“honeymadhatter”) shares her doc with targeted account(s) (“sam.burekas”) §  Only needs to know the targets’ email §  No email is sent, as the option can be unchecked
  • © 2014 Imperva, Inc. All rights reserved. Attack Setup: CSRF Page 37 §  Attacker adds an invisible CSRF link referencing to the attacker’s Google Doc to their online asset §  Asset can be •  A “watering hole” page •  A “phishing” page •  Etc. §  Invisible link example: •  “<script src = " https://docs.google.com/document/d/<some doc id>/edit"></ script>”
  • © 2014 Imperva, Inc. All rights reserved. Launching the Attack 38 §  When the intended target visits the CSRF page: •  The attacker uncovers victim’s identity (“sam.burekas”) instantly §  Can act accordingly: e.g. infect victim with malware
  • © 2014 Imperva, Inc. All rights reserved. Google’s Response 39
  • © 2014 Imperva, Inc. All rights reserved. Mitigations 40
  • © 2014 Imperva, Inc. All rights reserved. Consumers 41 §  Logout more! §  Use stricter privacy settings for vulnerable applications •  Full anonymity for LinkedIn §  Use personal Anti CSRF add-ons to block cross-site requests •  RequestPolicy •  CsFire •  NoScript
  • © 2014 Imperva, Inc. All rights reserved. Platform Providers §  Use standard CSRF protections •  Don’t allow a collaboration based on a single request from other domain §  Other domains can be determined by HTTP headers •  Referer •  Origin 42
  • © 2014 Imperva, Inc. All rights reserved. Platform Providers §  Single request collaboration, within same domain can be secured with a CSRF token •  Changing, un-guessable, unique identifier appended to the request §  Libraries exist to include this functionality in the code •  http://anticsrf.codeplex.com/ (.NET) •  https://www.owasp.org/index.php/ Category:OWASP_CSRFGuard_Project (Java, PHP, .NET) 43
  • © 2014 Imperva, Inc. All rights reserved. MS Seems to Get It Right 44
  • © 2014 Imperva, Inc. All rights reserved. Summary & Conclusion 45
  • © 2014 Imperva, Inc. All rights reserved. Summary 46 §  CSRF vulnerabilities of various types are common within applications §  CUSRF is a new type of CSRF that affects users of collaboration platforms and applications •  Disclosing the true identity of a victim, when accessing an attacker controlled application §  CUSRF can be used for fraud as well as “Ice Hole Phishing”
  • © 2014 Imperva, Inc. All rights reserved. Recommendations 47 §  Consumers •  Review privacy settings for collaboration platforms §  Providers •  Apply anti-CSRF mechanisms to collaboration activity
  • © 2014 Imperva, Inc. All rights reserved. Webinar Materials 48 Post-Webinar Discussions Answers to Attendee Questions Webinar Recording Link Join Group Join Imperva LinkedIn Group, Imperva Data Security Direct, for…
  • © 2014 Imperva, Inc. All rights reserved. www.imperva.com 49