Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page

Tobias Hartmann 0001

dblp:73/7038-1 · DBLP profile ↗
← Back
1ranked-venue papers
0as first author
0since 2021 · last 2012
—ORCID · unresolved

Domains — the database's venue-derived domains; a paper can count in several

Security and privacy · 1

Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.

Network and information security
1 paper
Systems and software security · 100%
Software engineering, system software, and programming languages
1 paper
Operating systems · 100%

Topics — the 4 heaviest of 5, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Systems and software security › exploitation › injection attacks
code injection attack
0.112012
Safe Loading - A Foundation for Secure Execution of Untrusted Programs · IEEE Symposium on Security and Privacy 2012
Systems and software security
exploitation
0.112012
Safe Loading - A Foundation for Secure Execution of Untrusted Programs · IEEE Symposium on Security and Privacy 2012
Systems and software security
memory safety
0.112012
Safe Loading - A Foundation for Secure Execution of Untrusted Programs · IEEE Symposium on Security and Privacy 2012
Systems and software security › isolation
software fault isolation
0.112012
Safe Loading - A Foundation for Secure Execution of Untrusted Programs · IEEE Symposium on Security and Privacy 2012

Methods — techniques the papers use, named apart from their topics

software-based fault isolation · 0.3control-flow integrity · 0.3
YearPublicationVenuePosition
2012 Safe Loading - A Foundation for Secure Execution of Untrusted Programs
abstract
The standard loader (ld.so) is a common target of attacks. The loader is a trusted component of the application, and faults in the loader are problematic, e.g., they may lead to local privilege escalation for SUID binaries. Software-based fault isolation (SFI) provides a framework to execute arbitrary code while protecting the host system. A problem of current approaches to SFI is that fault isolation is decoupled from the dynamic loader, which is treated as a black box. The sandbox has no information about the (expected) execution behavior of the application and the connections between different shared objects. As a consequence, SFI is limited in its ability to identify devious application behavior. This paper presents a new approach to run untrusted code in a user-space sandbox. The approach replaces the standard loader with a security-aware trusted loader. The secure loader and the sandbox together cooperate to allow controlled execution of untrusted programs. A secure loader makes security a first class concept and ensures that the SFI system does not allow any unchecked code to be executed. The user-space sandbox builds on the secure loader and subsequently dynamically checks for malicious code and ensures that all control flow instructions of the application adhere to an execution model. The combination of the secure loader and the user-space sandbox enables the safe execution of untrusted code in user-space. Code injection attacks are stopped before any unintended code is executed. Furthermore, additional information provided by the loader can be used to support additional security properties, e.g., in lining of Procedure Linkage Table calls reduces the number of indirect control flow transfers and therefore limits jump-oriented attacks. This approach implements a secure platform for privileged applications and applications reachable over the network that anticipates and confines security threats from the beginning.
Mathias Payer, Tobias Hartmann 0001, Thomas R. Gross
IEEE Symposium on Security and Privacy2