METHODS, SYSTEMS, AND COMPUTER READABLE MEDIA FOR DETECTING INJECTED MACHINE CODE

• US 20140181976A1
• Filed: 05/07/2012
• Published: 06/26/2014
• Est. Priority Date: 05/06/2011
• Status: Active Grant

• Current Assignee: University of North Carolina At Chapel Hill (University of North Carolina System)
• Original Assignee: University of North Carolina At Chapel Hill (University of North Carolina System)
• Inventors: Monrose, Fabian, Snow, Kevin, Krishnan, Srinivas
• Granted Patent: US 9,305,165 B2
• Time in Patent Office: Days
• US Class Current: 726/23
• CPC Class Codes: G06F 21/53 by executing in a restricted environment, e.g. sandbox or secure virtual machine
• CPC Class Codes: G06F 21/554 involving event detection and direct action
• CPC Class Codes: G06F 21/566 Dynamic detection, i.e. detection performed at run-time, e.g. emulation, suspicious activities

Abstract

According to one aspect, the subject matter described herein includes a method for detecting injected machine code. The method includes extracting data content from a buffer. The method also includes providing an operating system kernel configured to detect injected machine code. The method further includes executing, using the operating system kernel, the data content on a physical processor. The method further includes monitoring, using the operating system kernel, the execution of the data content to determine whether the data content contains injected machine code indicative of a code injection attack.

Claims

1. A method for detecting injected machine code, the method comprising:

extracting data content from a buffer;

providing an operating system kernel configured to detect injected machine code;

executing, using the operating system kernel, the data content on a physical processor; and

monitoring, using the operating system kernel, the execution of the data content to determine whether the data content contains injected machine code indicative of a code injection attack.

2. The method of claim 1 wherein the buffer is associated with at least one of a heap object, a network stream, a user file, and a multimedia platform object.

3. The method of claim 1 wherein executing the data content includes initiating execution from different offsets in the buffer.

4. The method of claim 1 comprising generating output specifying at least one of whether injected machine code was detected, a location in the buffer where injected machine code was detected, and a log of actions performed by detected injected machine code.

5. The method of claim 1 wherein executing the data content includes utilizing hardware virtualization.

6. The method of claim 5 wherein the hardware virtualization mediates processor events that cause a change in system state and allows guest instruction execution to occur directly on the processor.

7. The method of claim 1 wherein monitoring the execution of the data content includes tracing specific memory reads, writes, and executions via hardware-supported paging mechanisms.

8. The method of claim 1 wherein monitoring the execution of the data content includes flagging execution chains that do not cause execution faults.

9. The method of claim 1 wherein the operating system kernel is optimized for detecting injected machine code.

10. The method of claim 9 wherein the operating system kernel is configured to implement an arbitrary, operator defined, analysis heuristic for determining whether the instructions contain injected machine code indicative of a code injection attack.

11. The method of claim 10 wherein the analysis heuristic traces memory accesses to specific predefined locations.

12. The method of claim 1 comprising taking a snapshot of memory contents of processes at the time the buffer is created.

13. A system for detecting injected machine code, the system comprising:

an operating system kernel configured to detect injected machine code, wherein the operating system kernel includes;

a buffer execution module configured to extract data content from a buffer and execute, using the operating system kernel, the data content on a physical processor; and

an injected machine code analysis module configured to monitor, using the operating system kernel, the execution of the data content to determine whether the data content contains injected machine code indicative of a code injection attack.

14. The system of claim 13 wherein the buffer is associated with at least one of a heap object, a network stream, a user file, and a multimedia platform object.

15. The system of claim 13 wherein the buffer execution module is configured to execute the data content by initiating execution from different offsets in the buffer.

16. The system of claim 13 wherein the injected machine code analysis module is configured to generate output specifying at least one of whether injected machine code was detected, a location in the buffer where injected machine code was detected, and a log of actions performed by detected injected machine code.

17. The system of claim 13 wherein the buffer execution module is configured to execute the data content utilizing hardware virtualization.

18. The system of claim 17 wherein the hardware virtualization mediates processor events that cause a change in system state and allows guest instruction execution to occur directly on the processor.

19. The system of claim 13 wherein the injected machine code analysis module is configured to monitor the execution of the data content by tracing specific memory reads, writes, and executions via hardware-supported paging mechanisms.

20. The system of claim 13 wherein the injected machine code analysis module is configured to monitor the execution of the data content by flagging execution chains that do not cause execution faults.

21. The system of claim 13 wherein the operating system kernel is optimized for detecting injected machine code.

22. The system of claim 21 wherein the operating system kernel is configured to implement an arbitrary, operator defined, analysis heuristic for determining whether the instructions contain injected machine code indicative of a code injection attack.

23. The system of claim 22 wherein the analysis heuristic traces memory accesses to specific predefined locations.

24. The system of claim 13 wherein the buffer execution module is configured to take a snapshot of memory contents of processes at the time the buffer is created.

25. A non-transitory computer readable medium comprising computer executable instructions that when executed by a processor of a computer control the computer to perform steps comprising:

extracting data content from a buffer;

providing an operating system kernel configured to detect injected machine code;

executing, using the operating system kernel, the data content on a physical processor; and

monitoring, using the operating system kernel, the execution of the data content to determine whether the data content contains injected machine code indicative of a code injection attack.