DETECTING WEB BROWSER BASED ATTACKS USING BROWSER DIGEST COMPUTE TESTS LAUNCHED FROM A REMOTE SOURCE

• US 20120291129A1
• Filed: 03/23/2012
• Published: 11/15/2012
• Est. Priority Date: 05/13/2011
• Status: Active Grant

• Current Assignee: Imperva Incorporated (Thales SA)
• Original Assignee: Imperva Incorporated (Thales SA)
• Inventors: SHULMAN, AMICHAI, Be'ery, Tal Arieh
• Granted Patent: US 8,752,208 B2
• Time in Patent Office: Days
• US Class Current: 726/23
• CPC Class Codes: H04L 63/1433 Vulnerability analysis
• CPC Class Codes: H04L 63/145 the attack involving the propagation of malware through the network, e.g. viruses, trojans or worms
• 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 63/20 for managing network security; network security policies in general filtering policies H04L63/0227
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/561 Adding application-functional data or data for application control, e.g. adding metadata

Abstract

The detection of web browser-based attacks using browser tests launched from a remote source is described. In one example, a digest is computed based on the content of an HTTP response message. The message is modified and sent to a client device that also computes a digest. The digests are compared to determine whether content has been modified by malware on the HTTP client. The results of the test are analyzed and defensive measures are taken.

Claims

1-29. -29. (canceled)

30. A method performed in a security gateway coupled between an HTTP (Hypertext Transfer Protocol) client and a web application installed on a server, the method comprising:

receiving an HTTP response message from a web application server for delivery to an HTTP client, the response message including content;

computing a digest based on the content of the HTTP response message;

modifying the HTTP response message from the web application server to include code that when executed by a web browser on the HTTP client will cause the web browser to perform a test by computing a locally generated digest based on the HTTP response message it receives and return the locally generated digest to the security gateway;

sending to the HTTP client the modified HTTP response message;

receiving a test result message from the HTTP client, the test result message indicating the locally generated digest computed by the HTTP client wherein the digest and the locally generated digest will not match if malware has modified the content before reaching the web browser;

analyzing the test result message for an indication of malware on the HTTP client; and

taking defensive measures responsive to the analyzing.

31. The method of claim 30, further comprising establishing a session between the HTTP client and the web application server and wherein the taking defensive measures comprises marking the session as compromised.

32. The method of claim 30, further comprising receiving an HTTP request message, the HTTP request message being from the HTTP client and directed to the web application server and wherein the HTTP response message is in response to the HTTP request message.

33. The method of claim 32, further comprising transmitting the HTTP request to the web application server.

34. The method of claim 30, wherein the HTTP client includes a web browser and the computing the locally generated digest is performed by the web browser independent of any malware on the HTTP client.

35. The method of claim 30, wherein the taking defensive measures includes blocking messages from the HTTP client.

36. The method of claim 30, wherein the modified HTTP response message includes a test identifier to uniquely identify the test and wherein the code includes a command to return an indication of the test identifier.

37. The method of claim 36, wherein the test identifier includes an encrypted token generated using the computed digest and wherein the code includes a command to return the encrypted token.

38. The method of claim 30, wherein sending the modified HTTP response message includes sending a command to the HTTP client that when executed by a web browser on the HTTP client causes the web browser to perform the test operation with a remote server and to cause the remote server to forward the test results to the security gateway.

39. The method of claim 38, wherein the modified HTTP response message includes an indication of the digest, and wherein the sending a command includes sending a reference to the remote server and a command to send the indication of the digest to the remote server.

40. An apparatus comprising:

a network element including;

a security gateway module to receive an HTTP (Hypertext Transfer Protocol) response message from a web application server for delivery to an HTTP client, the response message including content;

wherein the security gateway module is further to perform a test with the HTTP client responsive to the received HTTP request message and a policy, wherein the performing includes;

computing a digest based on the content of the HTTP response message;

modifying the HTTP response message from the web application server to include code that when executed by a web browser on the HTTP client will cause the web browser to perform a test by computing a locally generated digest based on the HTTP response message it receives and return the locally generated digest to the security gateway;

sending to the HTTP client the modified HTTP response message; and

receiving a test result message from the HTTP client, the test result message indicating the locally generated digest computed by the HTTP client wherein the digest and the locally generated digest will not match if malware has modified the content before reaching the web browser;

wherein the security gateway module is further to analyze the test result for an indication of malware on the HTTP client; and

wherein the security gateway module is further to take defensive measures responsive to the analyzing.

42. The apparatus of claim 41, wherein the security gateway module is further to receive an HTTP request message, the HTTP request message being from an HTTP client and directed to a server on which a web application is installed and to determine whether the test is to be performed by detecting content in the request message that is commonly inserted by malware on an HTTP client;

43. The apparatus of claim 41, wherein the modified HTTP response further includes an encrypted token generated using the computed digest and wherein the code includes a command to return the encrypted token.

44. The apparatus of claim 41, wherein the HTTP client includes a web browser and the test operation is performed by the web browser independent of any malware on the HTTP client.

45. A machine-readable medium storing instructions that, when executed by the machine, cause the machine to perform operations comprising:

receiving an HTTP response message from a web application server for delivery to an HTTP client, the response message including content;

computing a digest based on the content of the HTTP response message;

modifying the HTTP response message from the web application server to include code that when executed by a web browser on the HTTP client will cause the web browser to perform a test by computing a locally generated digest based on the HTTP response message it receives and return the locally generated digest to the security gateway;

sending to the HTTP client the modified HTTP response message;

receiving a test result message from the HTTP client, the test result message indicating the locally generated digest computed by the HTTP client wherein the digest and the locally generated digest will not match if malware has modified the content before reaching the web browser;

analyzing the test result message for an indication of malware on the HTTP client; and

taking defensive measures responsive to the analyzing.

46. The medium of claim 45, the instructions further comprising establishing a session between the HTTP client and the web application server and wherein the taking defensive measures comprises marking the session as compromised.

47. The medium of claim 46, wherein the taking defensive measures includes blocking messages from the HTTP client.

48. The medium of claim 45, wherein sending the modified HTTP response message includes sending a command to the HTTP client that when executed by a web browser on the HTTP client causes the web browser to perform the test operation with a remote server and to cause the remote server to forward the test results to the security gateway.

49. The medium of claim 48, wherein the modified HTTP response message includes an indication of the digest, and wherein the sending a command includes sending a reference to the remote server and a command to send the indication of the digest to the remote server.