This rule was developed in part by Rachel Xu and Zifei (FeiFei) Han at the October 20-22, 2017 OurCS Workshop (http://www.cs.cmu.edu/ourcs/register.html).
For more information about this statement, see the About the OurCS Workshop page.
For OAuth, use a secure Android method to deliver access tokens. The method to do with mobile apps and their platforms is not specified in the OAuth 1.0 or OAuth 2.0 standards. Access tokens can be securely delivered if the service provider can identify recipients using a globally unique identifier.
Noncompliant Code Example
This noncompliant code example shows an application that
An Intent can securely send an access token to its intended mobile relying party app, using an explicit intent, because the relying party can be uniquely identified through its developer key hash.
In this compliant solution the application
Hyperlink black-font text "the CERT website" below, with URL as follows:
Search for vulnerabilities resulting from the violation of this rule on the CERT website.
Fill in the table below with at least one entry row, per these instructions, then remove this purple-font section.
Improper Validation of Certificate with Host Mismatch
OAuth Demystified for Mobile Application Developers. OAuthDemystified.pdf
Internet Engineering Task Force (IETF). OAuth core 1.0 revision a. http://oauth.net/core/1.0a/.
|[IETF OAuth2.0]||Internet Engineering Task Force (IETF). The OAuth 2.0 authorization framework. http://tools.ietf.org/html/rfc6749.|