Proceedings of the 14th ACM Conference on Computer and Communications Security 2007
DOI: 10.1145/1315245.1315260
|View full text |Cite
|
Sign up to set email alerts
|

Automated detection of persistent kernel control-flow attacks

Abstract: This paper presents a new approach to dynamically monitoring operating system kernel integrity, based on a property called state-based control-flow integrity (SBCFI). Violations of SBCFI signal a persistent, unexpected modification of the kernel's control-flow graph. We performed a thorough analysis of 25 Linux rootkits and found that 24 (96%) employ persistent control-flow modifications; an informal study of Windows rootkits yielded similar results. We have implemented SBCFI enforcement as part of the Xen and… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

3
144
0
1

Year Published

2010
2010
2015
2015

Publication Types

Select...
6
2

Relationship

1
7

Authors

Journals

citations
Cited by 218 publications
(148 citation statements)
references
References 26 publications
3
144
0
1
Order By: Relevance
“…In other words, an attacker could possibly launch a "return-into-libc" style attack or the so-called return-oriented attack [10,16,37] within the kernel by leveraging only the existing authenticated kernel code. Fortunately, solutions exist for protecting control flows [6,15,30,42] and data flow integrity [11] for user-level applications, which could be potentially extended to complement our system for kernel protection. Second, as with existing systems for kernel code integrity, our current implementation does not support self-modifying kernel code.…”
Section: Discussionmentioning
confidence: 99%
See 2 more Smart Citations
“…In other words, an attacker could possibly launch a "return-into-libc" style attack or the so-called return-oriented attack [10,16,37] within the kernel by leveraging only the existing authenticated kernel code. Fortunately, solutions exist for protecting control flows [6,15,30,42] and data flow integrity [11] for user-level applications, which could be potentially extended to complement our system for kernel protection. Second, as with existing systems for kernel code integrity, our current implementation does not support self-modifying kernel code.…”
Section: Discussionmentioning
confidence: 99%
“…As running inside a compromised operating system is dangerous, Copilot [28] copies operating system memory onto a PCI card for analysis by a dedicated coprocessor. Further extensions allow it to detect breaches of kernel data semantic integrity [29] and state-based control flow integrity [30]. Strider GhostBuster [40] and VMwatcher [17] aim to look for discrepancies between an internal and external view of a system to detect the hiding behavior from rootkits.…”
Section: Related Workmentioning
confidence: 99%
See 1 more Smart Citation
“…Virtual machine introspection (VMI). LIVEWIRE [12] demonstrated the concept of VMI and there is a significant amount of works that improve VMI for better practicality, automation, and wider applications such as VMWATCHER [15], SBCFI [28],VIR-TUOSO [13] and VMST [14]. The difference with SIGPATH is that these systems focus on kernel level introspection, whereas SIGPATH focuses on user level data introspection.…”
Section: Related Workmentioning
confidence: 99%
“…A number of malware protection proposals ( [10,16,23,25,31,40]) address the issue by using virtualization, creating a trusted zone from which their monitoring programs can operate and relying on a hypervisor to moderate between the host system and the monitor. These proposals, however, fail to take the inherent resource constraints of embedded control systems into account.…”
Section: The Problem With Virtualizationmentioning
confidence: 99%