OAuth Security Topics
draft-ietf-oauth-security-topics-04

Document Type Active Internet-Draft (oauth WG)
Last updated 2017-11-14
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Open Authentication Protocol                         T. Lodderstedt, Ed.
Internet-Draft                                                YES.com AG
Intended status: Best Current Practice                        J. Bradley
Expires: May 17, 2018                                             Yubico
                                                             A. Labunets
                                                                Facebook
                                                       November 13, 2017

                         OAuth Security Topics
                  draft-ietf-oauth-security-topics-04

Abstract

   This draft gives a comprehensive overview on open OAuth security
   topics.  It is intended to serve as a working document for the OAuth
   working group to systematically capture and discuss these security
   topics and respective mitigations and eventually recommend best
   current practice and also OAuth extensions needed to cope with the
   respective security threats.

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 https://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 May 17, 2018.

Copyright Notice

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

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://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

Lodderstedt, et al.       Expires May 17, 2018                  [Page 1]
Internet-Draft               Security Topics               November 2017

   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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Best Practices  . . . . . . . . . . . . . . . . . . . . . . .   4
     2.1.  Protecting redirect-based flows . . . . . . . . . . . . .   4
     2.2.  Token Leakage Prevention  . . . . . . . . . . . . . . . .   5
   3.  Recommended Changes to OAuth  . . . . . . . . . . . . . . . .   5
   4.  Attacks and Mitigations . . . . . . . . . . . . . . . . . . .   5
     4.1.  Insufficient redirect URI validation  . . . . . . . . . .   5
       4.1.1.  Attacks on Authorization Code Grant . . . . . . . . .   6
       4.1.2.  Attacks on Implicit Grant . . . . . . . . . . . . . .   7
       4.1.3.  Proposed Countermeasures  . . . . . . . . . . . . . .   8
     4.2.  Authorization code leakage via referrer headers . . . . .   9
       4.2.1.  Proposed Countermeasures  . . . . . . . . . . . . . .  10
     4.3.  Attacks in the Browser  . . . . . . . . . . . . . . . . .  10
       4.3.1.  Code in browser history (TBD) . . . . . . . . . . . .  10
       4.3.2.  Access token in browser history (TBD) . . . . . . . .  10
       4.3.3.  Javascript Code stealing Access Tokens (TBD)  . . . .  11
     4.4.  Mix-Up  . . . . . . . . . . . . . . . . . . . . . . . . .  11
     4.5.  Code Injection  . . . . . . . . . . . . . . . . . . . . .  11
       4.5.1.  Proposed Countermeasures  . . . . . . . . . . . . . .  13
     4.6.  XSRF (TBD)  . . . . . . . . . . . . . . . . . . . . . . .  15
     4.7.  Access Token Leakage at the Resource Server . . . . . . .  15
       4.7.1.  Access Token Phishing by Counterfeit Resource Server   15
         4.7.1.1.  Metadata  . . . . . . . . . . . . . . . . . . . .  16
         4.7.1.2.  Sender Constrained Access Tokens  . . . . . . . .  17
         4.7.1.3.  Audience Restricted Access Tokens . . . . . . . .  19
       4.7.2.  Compromised Resource Server . . . . . . . . . . . . .  20
     4.8.  Refresh Token Leakage (TBD) . . . . . . . . . . . . . . .  21
     4.9.  Open Redirection (TBD)  . . . . . . . . . . . . . . . . .  21
     4.10. TLS Terminating Reverse Proxies . . . . . . . . . . . . .  22
     4.11. Other Topics  . . . . . . . . . . . . . . . . . . . . . .  22
   5.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  23
Show full document text