Security Considerations for WebRTC
draft-ietf-rtcweb-security-08

 
Document
Type Active Internet-Draft (rtcweb WG)
Last updated 2015-03-19 (latest revision 2015-02-26)
Replaces draft-rescorla-rtcweb-security
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf html
Stream
WG state Waiting for WG Chair Go-Ahead Mar 2014
Doc Shepherd Follow-up Underway
Document shepherd spt
Shepherd write-up Show (last changed 2015-03-19)
IESG
IESG state Publication Requested
Telechat date
Responsible AD Alissa Cooper
Send notices to rtcweb-chairs@ietf.org, draft-ietf-rtcweb-security@ietf.org, draft-ietf-rtcweb-security.shepherd@ietf.org, draft-ietf-rtcweb-security.ad@ietf.org, turners@ieca.com

Email authors IPR References Referenced by Nits Search lists

RTC-Web                                                      E. Rescorla
Internet-Draft                                                RTFM, Inc.
Intended status: Standards Track                       February 26, 2015
Expires: August 30, 2015

                   Security Considerations for WebRTC
                     draft-ietf-rtcweb-security-08

Abstract

   The Real-Time Communications on the Web (RTCWEB) working group is
   tasked with standardizing protocols for real-time communications
   between Web browsers, generally called "WebRTC".  The major use cases
   for WebRTC technology are real-time audio and/or video calls, Web
   conferencing, and direct data transfer.  Unlike most conventional
   real-time systems (e.g., SIP-based soft phones) WebRTC communications
   are directly controlled by a Web server, which poses new security
   challenges.  For instance, a Web browser might expose a JavaScript
   API which allows a server to place a video call.  Unrestricted access
   to such an API would allow any site which a user visited to "bug" a
   user's computer, capturing any activity which passed in front of
   their camera.  This document defines the WebRTC threat model and
   analyzes the security threats of WebRTC in that model.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on August 30, 2015.

Copyright Notice

   Copyright (c) 2015 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

Rescorla                 Expires August 30, 2015                [Page 1]
Internet-Draft               WebRTC Security               February 2015

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

   This document may contain material from IETF Documents or IETF
   Contributions published or made publicly available before November
   10, 2008.  The person(s) controlling the copyright in some of this
   material may not have granted the IETF Trust the right to allow
   modifications of such material outside the IETF Standards Process.
   Without obtaining an adequate license from the person(s) controlling
   the copyright in such materials, this document may not be modified
   outside the IETF Standards Process, and derivative works of it may
   not be created outside the IETF Standards Process, except to format
   it for publication as an RFC or to translate it into languages other
   than English.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  The Browser Threat Model  . . . . . . . . . . . . . . . . . .   4
     3.1.  Access to Local Resources . . . . . . . . . . . . . . . .   5
     3.2.  Same Origin Policy  . . . . . . . . . . . . . . . . . . .   6
     3.3.  Bypassing SOP: CORS, WebSockets, and consent to
           communicate . . . . . . . . . . . . . . . . . . . . . . .   6
   4.  Security for WebRTC Applications  . . . . . . . . . . . . . .   7
     4.1.  Access to Local Devices . . . . . . . . . . . . . . . . .   7
       4.1.1.  Threats from Screen Sharing . . . . . . . . . . . . .   8
       4.1.2.  Calling Scenarios and User Expectations . . . . . . .   9
         4.1.2.1.  Dedicated Calling Services  . . . . . . . . . . .   9
         4.1.2.2.  Calling the Site You're On  . . . . . . . . . . .   9
       4.1.3.  Origin-Based Security . . . . . . . . . . . . . . . .  10
       4.1.4.  Security Properties of the Calling Page . . . . . . .  11
     4.2.  Communications Consent Verification . . . . . . . . . . .  12
       4.2.1.  ICE . . . . . . . . . . . . . . . . . . . . . . . . .  13
       4.2.2.  Masking . . . . . . . . . . . . . . . . . . . . . . .  13
Show full document text