Systems and methods for intrusion detection and prevention using software patching and honeypots
A variety of methods are provided for an application or operating system (OS) kernel intrusion detection and prevention, based on usage of existing vulnerability fixes and their transformation into honeypot detectors. A honeypot patch may be generated for a computing system associated with a software vulnerability in software installed on the computing system. The honeypot patch, when used to modify the installed software, can convert the computing system into a honeypot system configured to detect attempts to exploit the software vulnerability of the software, and in response, generate a security event associated with the software vulnerability.
1. A computer-implemented method for software intrusion detection, comprising:
generating a honeypot patch for a computing system associated with a software vulnerability in a software installed on the computing system, wherein the software comprises at least one of an application and an operating system,
wherein the honeypot patch is configured to convert the computing system associated with the software vulnerability into a honeypot system by modifying code of the software running on the computing system using the generated honeypot patch without restarting the software, wherein the generated honeypot patch is a live patch that updates the code of the software without interruption in execution of the software, and wherein the honeypot system is configured to detect attempts to exploit the software vulnerability of the software, and in response, generate a security event associated with the software vulnerability.
2. The method of claim 1 , wherein the honeypot patch comprises computer-executable instructions configured to detect the attempt to exploit the software vulnerability of the software using a conditional test for verifying security capability to be inserted into the original source code of the software.
3. The method of claim 1 , wherein the honeypot patch comprises computer-executable instructions configured to detect the attempt to exploit the software vulnerability of the software using a conditional test for whether the attempt is to cause a buffer overflow.
4. The method of claim 1 , wherein the software vulnerability comprises a memory use after free vulnerability.
5. The method of claim 4 , wherein the honeypot patch comprises computer-executable instructions configured to detect the attempt to exploit the software vulnerability of the software by:
marking a data structure with a predetermined placeholder value; and
verifying that the data structure does not contain the predetermined placeholder value.
6. The method of claim 1 , wherein the software vulnerability comprises a race condition.
7. The method of claim 6 , wherein the honeypot patch comprises computer-executable instructions configured to detect the attempt to exploit the software vulnerability of the software using a set of conditional tests leading up to the race and software state manipulation.
8. The method of claim 1 , wherein the honeypot system configured to detect attempts to exploit the software vulnerability of the software is further configured to report the exploit attempts to a system administrator via a notification.
9. The method of claim 1 , wherein the honeypot system is further configured to, in response to detecting attempts to exploit the software vulnerability of the software, kill and block intruder processes.
10. The method of claim 1 , wherein the honeypot system is further configured to, in response to detecting attempts to exploit the software vulnerability of the software, save a state of processes running on the honeypot system for further analysis.
11. The method of claim 1 , wherein the honeypot system is further configured to, in response to detecting attempts to exploit the software vulnerability of the software, live migrate processes associated with the detected attack to an isolated system or a virtual machine.
12. The method of claim 11 , wherein current or future connections from an attacking address are routed to the isolated system or the virtual machine where the processes were migrated.
13. The method of claim 1 , wherein the honeypot system is further configured to, in response to detecting attempts to exploit the software vulnerability of the software, block a login of a user associated with the detected attack.
14. The method of claim 1 , wherein the honeypot system is further configured to, in response to detecting attempts to exploit the software vulnerability of the software, block at least a portion of network traffic from an original network address associated with the detected attack.
15. The method of claim 1 , wherein the honeypot system is further configured to, in response to detecting attempts to exploit the software vulnerability of the software, fake to the attacker that the detected attack was successful.
16. A system for software intrusion detection, comprising:
a hardware processor configured to:
generate a honeypot patch for a computing system associated with a software vulnerability in a software installed on the computing system, wherein the software comprises at least one of an application and an operating system,
wherein the honeypot patch is configured to convert the computing system associated with the software vulnerability into a honeypot system by modifying code of the software running on the computing system using the generated honeypot patch without restarting the software, wherein the generated honeypot patch is a live patch that updates the code of the software without interruption in execution of the software, and wherein the honeypot system is configured to detect attempts to exploit the software vulnerability of the software, and in response, generate a security event associated with the software vulnerability.
17. A non-transitory computer readable medium comprising computer executable instructions for software intrusion detection, including instructions for:
generating a honeypot patch for a computing system associated with a software vulnerability in a software installed on the computing system, wherein the software comprises at least one of an application and an operating system,
wherein the honeypot patch is configured to convert the computing system associated with the software vulnerability into a honeypot system by modifying code of the software running on the computing system using the generated honeypot patch without restarting the software, wherein the generated honeypot patch is a live patch that updates the code of the software without interruption in execution of the software, and wherein the honeypot system is configured to detect attempts to exploit the software vulnerability of the software, and in response, generate a security event associated with the software vulnerability.