OAuth Security Topics
draft-ietf-oauth-security-topics-03
|
| Document |
Type |
|
Active Internet-Draft (oauth WG)
|
|
Last updated |
|
2017-09-10
|
|
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 Europe AG
Intended status: Best Current Practice J. Bradley
Expires: March 14, 2018 Yubico
A. Labunets
Facebook
September 10, 2017
OAuth Security Topics
draft-ietf-oauth-security-topics-03
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 March 14, 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 March 14, 2018 [Page 1]
Internet-Draft Security Topics September 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. Recommended Best Practice . . . . . . . . . . . . . . . . . . 4
2.1. Protecting redirect-based flows . . . . . . . . . . . . . 4
2.2. TBD . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
3. Recommended modifications and extensions to OAuth . . . . . . 5
4. OAuth Credentials Leakage . . . . . . . . . . . . . . . . . . 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 . . . . . 10
4.2.1. Proposed Countermeasures . . . . . . . . . . . . . . 10
4.3. Attacks in the Browser . . . . . . . . . . . . . . . . . 10
4.3.1. Code in browser history (TBD) . . . . . . . . . . . . 11
4.3.2. Access token in browser history (TBD) . . . . . . . . 11
4.3.3. Javascript Code stealing Access Tokens (TBD) . . . . 11
4.4. Access Token Leakage at the Resource Server . . . . . . . 11
4.4.1. Access Token Phishing by Counterfeit Resource Server 11
4.4.1.1. Metadata . . . . . . . . . . . . . . . . . . . . 12
4.4.1.2. Sender Constrained Access Tokens . . . . . . . . 13
4.4.1.3. Audience Restricted Access Tokens . . . . . . . . 15
4.4.2. Compromised Resource Server . . . . . . . . . . . . . 16
4.4.3. TLS Terminating Reverse Proxies . . . . . . . . . . . 17
4.5. Mix-Up . . . . . . . . . . . . . . . . . . . . . . . . . 18
4.6. Refresh Token Leakage . . . . . . . . . . . . . . . . . . 18
5. OAuth Credentials Injection . . . . . . . . . . . . . . . . . 19
5.1. Code Injection . . . . . . . . . . . . . . . . . . . . . 19
5.1.1. Proposed Countermeasures . . . . . . . . . . . . . . 21
5.2. Access Token Injection (TBD) . . . . . . . . . . . . . . 22
5.3. XSRF (TBD) . . . . . . . . . . . . . . . . . . . . . . . 23
6. Other Attacks . . . . . . . . . . . . . . . . . . . . . . . . 23
Show full document text