Systrace
 | This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these template messages)
|
| Original author(s) | Niels Provos |
|---|---|
| Stable release | 1.6g
/ March 15, 2009 |
| Operating system | Unix-like |
| Type | Computer security |
| License | BSD-like |
| Website | www |
Systrace is a computer security utility which limits an application's access to the system by enforcing access policies for system calls. This can mitigate the effects of buffer overflows and other security vulnerabilities. It was developed by Niels Provos and runs on various Unix-like operating systems.
Systrace is particularly useful when running untrusted or binary-only applications and provides facilities for privilege elevation on a system call basis, helping to eliminate the need for potentially dangerous setuid programs. It also includes interactive and automatic policy generation features, to assist in the creation of a base policy for an application.
Systrace used to be integrated into OpenBSD, but was removed in April 2016[1][2] (in favour of pledge post OpenBSD 5.9[3][4]). It is available for Linux and Mac OS X, although the OS X port is currently unmaintained. It was removed from NetBSD at the end of 2007 due to several unfixed implementation issues. As of version 1.6f Systrace supports 64-bit Linux 2.6.1 via kernel patch.
Features
[edit]Systrace supports the following features:
- Confines untrusted binary applications: An application is allowed to make only those system calls specified as permitted in the policy. If the application attempts to execute a system call that is not explicitly permitted, an alarm gets raised.
- Interactive policy generation with graphical user interface: Policies can be generated interactively via a graphical frontend to Systrace. The frontend shows system calls and their parameters not currently covered by policy and allows the user to refine the policy until it works as expected.
- Supports different emulations: Linux, BSDI, etc..
- Non-interactive policy enforcement: Once a policy has been trained, automatic policy enforcement can be used to deny all system calls not covered by the current policy. All violations are logged to Syslog. This mode is useful when protecting system services like a web server.
- Remote monitoring and intrusion detection: Systrace supports multiple frontends by using a frontend that makes use of the network, very advanced features are possible.
- Privilege elevation: Using Systrace's privilege elevation mode, it's possible to get rid of setuid binaries. A special policy statement allows selected system calls to run with higher privileges, for example, creating a raw socket.
Vulnerability history
[edit]Systrace has had some vulnerabilities in the past, including:
- Exploiting Concurrency Vulnerabilities in System Call Wrappers Paper by Robert Watson from the First USENIX Workshop On Offensive Technologies (WOOT07) analyzing system call wrapper traces across several wrapper platforms including systrace
- Google Security discovers local privilege escalation in Systrace
- Local root exploit on NetBSD
- Vulnerabilities in systrace
See also
[edit]References
[edit]- ^ Unangst, Ted (25 April 2016). "boom goes the dynamite". openbsd-cvs (Mailing list). Retrieved 17 May 2016.
- ^ Unangst, Ted (25 April 2016). "remove systrace". openbsd-cvs (Mailing list). Retrieved 17 May 2016.
- ^ "OpenBSD Innovations". OpenBSD. 2018-08-14. Retrieved 2019-02-26.
systrace(4), systrace(1): Started by Niels Provos. Imported June 4, 2002 and first released with OpenBSD 3.2. Deleted after OpenBSD 5.9 because pledge(2) is even better.
- ^ Nicholas Marriott; Theo de Raadt (2019-02-14). "sys/kern/kern_pledge.c". BSD Cross Reference. OpenBSD. Retrieved 2019-02-26.