Cross-site request forgery defense

• US 9,774,622 B2
• Filed: 04/24/2017
• Issued: 09/26/2017
• Est. Priority Date: 08/07/2015
• Status: Active Grant

• Current Assignee: Adobe Inc.
• Original Assignee: Adobe Systems Incorporated (Adobe Inc.)
• Inventors: Krapf, Lars, Knobloch, Gilles, Antipa, Damien, Leonardo, Christanto, Sanso, Antonio
• Primary Examiner(s): Cribbs, Malcolm
• Application Number:
  US15/494,623
• Publication Number:
  US 20170223051A1
• Time in Patent Office: 155 Days
• Field of Search: None
• CPC Class Codes: G06F 21/44 Program or device authentication
• CPC Class Codes: G06F 2221/2119 Authenticating web pages, e.g. with suspicious links
• CPC Class Codes: G06F 2221/2129 Authenticate client device independently of the user
• CPC Class Codes: H04L 63/10 for controlling access to devices or network resources
• CPC Class Codes: H04L 63/123 received data contents, e.g. message integrity
• CPC Class Codes: H04L 63/1466 Active attacks involving interception, injection, modification, spoofing of data unit addresses, e.g. hijacking, packet injection or TCP sequence number attacks
• CPC Class Codes: H04L 9/3213 using tickets or tokens, e.g. Kerberos network architectures or network communication protocols for entities authentication using tickets in a packet data network H04L63/0807
• CPC Class Codes: H04L 9/3234 involving additional secure or trusted devices, e.g. TPM, smartcard, USB or software token network architectures or network communication protocols for supporting authentication of entities using an additional device in a packet data network H04L63/0853
• CPC Class Codes: H04L 9/3242 involving keyed hash functions, e.g. message authentication codes [MACs], CBC-MAC or HMAC

Abstract

An HTML document includes a JavaScript element that manages CSRF token use. When the HTML document is rendered, the JavaScript element asynchronously requests a CSRF token from the server. In response, the server generates a JWT using a keyed HMAC algorithm. The resulting JWT, which functions as a CSRF token, is returned to the user where it is stored in a protected variable inside the JavaScript element. The CSRF token is therefore stateless and isn'"'"'t stored in a server-side repository. When the user later requests access to a server resource, the CSRF token is included in such request. This may be accomplished by adding a hidden input field that includes the CSRF token to the submission that'"'"'s transmitted to the server. If the server cannot validate the received token using the HMAC key that was originally used to generate the token, the request is considered unauthorized and is not processed.

Claims

1. A computer-implemented method for defending against a cross-site request forgery (CSRF) attack, the method comprising:

serving a content item to a client computing device, wherein the content item includes an embedded executable script;

receiving a first asynchronous request for a first CSRF token from the client computing device, wherein the first asynchronous request is generated as a result of running the embedded executable script at the client computing device;

generating the first CSRF token in response to the first asynchronous request, wherein the first CSRF token is generated using a hash message authentication code (HMAC) key;

sending the first CSRF token to the client computing device;

receiving a second asynchronous request for a second CSRF token from the embedded executable script of the client computing device, wherein the second asynchronous request is received after sending the first CSRF token to the client computing device;

generating the second CSRF token in response to the second asynchronous request, wherein the second CSRF token is also generated using the HMAC key;

sending the second CSRF token to the client computing device;

receiving, from the client computing device, a request to access a resource provided by a server computing device, wherein the request includes a received CSRF token; and

determining whether the received CSRF token can be authenticated using the HMAC key.

2. The method of claim 1, wherein:

a first server computing device generates the first and second CSRF tokens; and

a second server computing device determines whether the received CSRF token can be authenticated using the HMAC key.

3. The method of claim 1, wherein the first and second CSRF tokens are not retained at the server computing device after they are sent to the client computing device.

4. The method of claim 1, wherein the content item is an HTML document that is served to the client computing device from a web browser.

5. The method of claim 1, wherein the embedded executable script is a JavaScript element.

6. The method of claim 1, further comprising granting access to the resource in response to determining that the received CSRF token can be authenticated using the HMAC key.

7. The method of claim 1, wherein the first and second CSRF tokens are each subject to an expiration event.

8. A cross-site request forgery (CSRF) defense system that comprises a server cluster having a plurality of server computing devices, each of the server computing devices including

a processor, wherein the plurality of processors are configured to collectively execute instructions that cause the server cluster to invoke a CSRF defense process;

and

a memory storing a hash message authentication code (HMAC) key, wherein the HMAC key stored in each of the memories is functionally equivalent;

wherein the CSRF defense process comprises;

serving a content item to a client computing device, wherein the content item includes an executable script;

receiving a first request for a first CSRF token from the client computing device, wherein the first request is generated in response to running the executable script at the client computing device;

generating the first CSRF token in response to the first request, wherein the first CSRF token is generated using a particular one of the HMAC keys;

sending the first CSRF token to the client computing device;

receiving a second request for an updated CSRF token from the embedded executable script of the client computing device, wherein the second request is received after sending the first CSRF token to the client computing device;

generating the updated CSRF token in response to the second request, wherein the updated CSRF token is also generated using the particular HMAC key;

sending the second CSRF token to the client computing device;

receiving, from the client computing device, a subsequent request to access a resource provided by one of the server computing devices, wherein the subsequent request includes a received CSRF token; and

determining whether the received CSRF token can be authenticated using one of the HMAC keys.

9. The CSRF defense system of claim 8, wherein the first CSRF token is subject to an expiration event, and wherein the expiration event occurs at a time when the client computing device cannot communicate with the server cluster.

10. The CSRF defense system of claim 8, wherein the CSRF defense process further comprises, in response to determining that the received CSRF token cannot be authenticated using the HMAC keys, sending the client computing device an error message indicating that access to the resource is denied.

11. The CSRF defense system of claim 8, wherein the first request is generated at the client computing device in response to a user interaction with the content item at the client computing device.

12. The CSRF defense system of claim 8, further comprising a load balancer that routes the first and second requests to different server computing devices.

13. The CSRF defense system of claim 8, wherein the first CSRF token and the updated CSRF token are different.

14. A computer program product comprising a non-transitory computer readable medium storing instructions that, when executed by one or more processors, causes a cross-site request forgery (CSRF) defense process to be carried out, the process comprising:

requesting a content item from a server cluster;

receiving the requested content item from the server cluster, wherein the received content item includes a JavaScript element, and wherein the content item is received by a client computing device;

rendering the received content item in a content browser running on the client computing device;

in response to executing the JavaScript element at the first client computing device, requesting a first CSRF token from the server cluster;

receiving the first CSRF token from the server cluster, wherein the first CSRF token is received by the client computing device;

after receiving the first CSRF token from the server cluster, making a determination that network connectivity between the client computing device and the server cluster is unavailable;

detecting that the network connectivity between the client computing device and the server cluster has been reestablished;

in response to detecting that network connectivity has been reestablished, and as a result of executing the JavaScript element, requesting a second CSRF token from the server cluster;

receiving the second CSRF token from the server cluster, wherein the second CSRF token is received by the client computing device; and

submitting, to the server cluster, a request for access to a resource provided by the server cluster, wherein the request includes the second CSRF token that was received from the server cluster.

15. The computer program product of claim 14, wherein the content item is a fillable form, and the access request includes data that is to be submitted to the server cluster using the fillable form.

16. The computer program product of claim 14, wherein submitting the access request to the server cluster comprises:

monitoring a capture phase of the content browser;

detecting a submit event generated in response to a user interaction with the content browser; and

adding a hidden input field to the content item, wherein the hidden input field includes the second CSRF token.

17. The computer program product of claim 14, wherein the CSRF defense process further comprises storing the second received CSRF token in a protected variable that is defined in the JavaScript element.

18. The computer program product of claim 14, wherein requesting the content item from the server cluster comprises submitting an initial request for the content item to a load balancer configured to route the initial request to one of a plurality of server computing devices comparing the server cluster.

19. The computer program product of claim 14, wherein the JavaScript element is executed in response to rendering the content item in the content browser.