MONITORING AND MITIGATING CLIENT-SIDE EXPLOITATION OF APPLICATION FLAWS

• US 20150249678A1
• Filed: 05/14/2015
• Published: 09/03/2015
• Est. Priority Date: 01/28/2013
• Status: Active Grant

• Current Assignee: Hewlett Packard Enterprise Development LP (Hewlett-Packard Enterprise Company)
• Original Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Inventors: Decime, Jerry Brent, Smith, Cale Stefan
• Granted Patent: US 9,602,534 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 21/52 during program execution, e.g. stack integrity ; Preventing unwanted data erasure; Buffer overflow
• CPC Class Codes: G06F 21/57 Certifying or maintaining trusted computer platforms, e.g. secure boots or power-downs, version controls, system software checks, secure updates or assessing vulnerabilities
• CPC Class Codes: G06F 2221/033 Test or assess software
• CPC Class Codes: H04L 63/1416 Event detection, e.g. attack signature detection
• CPC Class Codes: H04L 63/1441 Countermeasures against malicious traffic countermeasures against attacks on cryptographic mechanisms H04L9/002

Abstract

A system for monitoring and mitigating client-side exploitation of application flaws includes a server to operate a first application. The first application communicates with a client device operating a second application to execute an application flaw script. The application flaw script causes the client device to produce a first request associated with vulnerability of the first application. An application flaw service module, communicatively coupled to the server, receives the first request from the client device comprising transactional metadata based on the application flaw script and inspects the transactional metadata for malicious content within the first request.

Claims

1. A system for monitoring and mitigating client-side exploitation of application flaws, the system comprising:

a server to operate a first application, the first application to communicate with a client device operating a second application to execute an application flaw script and the application flaw script to cause the client device to produce a first request associated with vulnerability of the first application; and

an application flaw service module communicatively coupled to the server, the application flaw service module to;

receive the first request from the client device comprising transactional metadata based on the application flaw script; and

inspect the transactional metadata for malicious content within the first request.

2. The system of claim 1, in which the first request is a GET request and in which the first application is a web-application.

3. The system of claim 1, which prior to the application flaw service module receiving and inspecting the transactional metadata within the first request, the server causes the application flaw script to be added to the transactional metadata of a response to a second request sent by the client device.

4. The system of claim 3, in which the second application is a browser and the browser on the client device executes the application flaw script and generates the first request to the application flaw service module based on the application flaw script.

5. The system of claim 1, in which the application flaw service module further generates a countermeasure script and response and sends the response to the client device for execution of the countermeasures.

6. The system of claim 1, in which the application flaw service module inspects, with a header and location inspection module, the transactional metadata for malicious content within the first request by referring to a filter rules and logic database.

7. The system of claim 6, further comprising a vulnerability tracking module that tracks attack vectors in the received requests that are detected by the header and location inspection module.

8. The system of claim 1, wherein prior to the application flaw service module receiving and inspecting the transactional metadata within the first request, the server is to cause the application flaw script to be added to the transactional metadata of a response to a second request sent by the client device and wherein the application flaw service module is to inspect, with a header and location inspection module, the transactional metadata for malicious content within the first request by referring to a filter rules and logic database.

9. A method of monitoring and mitigating client-side exploitation of application flaws comprising:

adding computer usable program code to the beginning of a first response to a first request from a client, the computer usable program code to perform a basic inspection of the first response;

receiving a second request from the client;

determining that transactional metadata within the second request response contains an attack vector; and

returning a second response to the second request to the client including attack vector countermeasures embedded in the second response.

10. The method of claim 9, further comprising tracking a type of vulnerability as evidenced by the attack vector.

11. The method of claim 9, in which the first and second requests are GET requests originating from a client device executing a web-application.

12. The method of claim 9, in which determining that the transactional metadata of the first response contains an attack vector further comprises comparing a number of filter rules and logic from a filter rules and logic database with the content of the request to determine if the first response contains an attack vector.

13. The method of claim 9, in which the computer usable program code added to the beginning of the first response to a first request is executed by a client device and in which the client device generates and sends the second request.

14. The method of claim 9, wherein the computer usable program code added to the beginning of the first response to the first request from the client to perform a basic inspection of the first response comprises an application flaw script added to transactional metadata of the first response, wherein the second request received from the client comprises the transactional metadata based on the application flaw script and wherein determining whether the transactional metadata within the second request contains malicious content comprising an attack vector is by inspecting the transactional metadata in a header of the second request using a header and location inspection module that refers to a filter rules and logic database.

15. A computer program product for monitoring and mitigating client-side exploitation of application flaws, the computer program product comprising:

a non-transitory computer readable storage medium comprising computer usable program code embodied therewith, the computer usable program code comprising;

computer usable program code to, when executed by a processor, add computer usable program code to a beginning of a first response to a first request from a client, the computer usable program code to perform a basic inspection of the first response;

computer usable program code to, when executed by a processor, receive a second request from the client;

computer usable program code to, when executed by a processor, determine that transactional metadata within the second request contains an attack vector; and

computer usable program code to, when executed by a processor, return a second response to the second request to the client including attack vector countermeasures embedded in the response.

16. The computer program product of claim 15, further comprising computer usable program code to, when executed by a processor, track a type of vulnerability as evidenced by the attack vector.

17. The computer program product of claim 15, in which the computer usable program code to determine that the transactional metadata of the first response contains an attack vector further comprises computer usable program code to, when executed by a processor, compare a number of filter rules and logic from a filter rules and logic database with the content of the request to determine if the first response contains an attack vector.

18. The computer program product of claim 15, wherein the computer usable program code added to the beginning of the first response to the first request from the client to perform a basic inspection of the first response comprises an application flaw script added to transactional metadata of the first response, wherein the second request received from the client comprises the transactional metadata based on the application flaw script and wherein determining whether the transactional metadata within the second request contains malicious content comprising an attack vector is by inspecting the transactional metadata in a header of the second request using a header and location inspection module that refers to a filter rules and logic database.