Demo Data from EDBT 2026 / reviewers in the wild / expert
Christopher Jelesnianski
dblp:161/0183
· DBLP profile ↗
7ranked-venue papers
2as first author
4since 2021 · last 2024
0000-0002-8067-2151ORCID · verified
Domains — the database's venue-derived domains; a paper can count in several
Systems, architecture and hardware · 5 · 2 first-author · 2 since 2021Software engineering, systems software and programming languages · 3 · 1 first-author · 2 since 2021Security and privacy · 2 · 2 since 2021
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
4 papers |
Systems and software security · 100% | |
| Computer architecture, parallel and distributed computing, and storage systems
2 papers |
Processor architecture and microarchitecture · 43% Cloud and datacenter computing · 25% Distributed systems · 25% | |
| Software engineering, system software, and programming languages
1 paper |
Operating systems · 77% Compilers and program optimization · 23% |
Topics — the 17 heaviest of 20, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Systems and software security
memory safety |
1.3 | 2 | 2024 | Enforcing C/C++ Type and Scope at Runtime for Control-Flow and Data-Flow Integrity · ASPLOS (3) 2024 VIP: Safeguard Value Invariant Property for Thwarting Critical Memory Corruption Attacks · CCS 2021 |
Systems and software security › memory safety
control-flow integrity |
0.9 | 2 | 2024 | Enforcing C/C++ Type and Scope at Runtime for Control-Flow and Data-Flow Integrity · ASPLOS (3) 2024 VIP: Safeguard Value Invariant Property for Thwarting Critical Memory Corruption Attacks · CCS 2021 |
Systems and software security › data integrity
data-flow integrity |
0.8 | 1 | 2024 | Enforcing C/C++ Type and Scope at Runtime for Control-Flow and Data-Flow Integrity · ASPLOS (3) 2024 |
Systems and software security › exploitation
control-flow hijacking |
0.7 | 2 | 2023 | VIP: Safeguard Value Invariant Property for Thwarting Critical Memory Corruption Attacks · CCS 2021 Protect the System Call, Protect (Most of) the World with BASTION · ASPLOS (3) 2023 |
Systems and software security
operating system security |
0.7 | 1 | 2023 | Protect the System Call, Protect (Most of) the World with BASTION · ASPLOS (3) 2023 |
Systems and software security › operating system security
system call protection |
0.7 | 1 | 2023 | Protect the System Call, Protect (Most of) the World with BASTION · ASPLOS (3) 2023 |
Systems and software security › memory safety › hardware-enforced memory safety
memory tagging |
0.6 | 1 | 2022 | Tightly Seal Your Sensitive Pointers with PACTight · USENIX Security Symposium 2022 |
Systems and software security › memory safety
pointer integrity |
0.6 | 1 | 2022 | Tightly Seal Your Sensitive Pointers with PACTight · USENIX Security Symposium 2022 |
Systems and software security › exploitation
memory corruption attack |
0.5 | 1 | 2021 | VIP: Safeguard Value Invariant Property for Thwarting Critical Memory Corruption Attacks · CCS 2021 |
Systems and software security › memory safety
memory corruption defense |
0.5 | 1 | 2021 | VIP: Safeguard Value Invariant Property for Thwarting Critical Memory Corruption Attacks · CCS 2021 |
Distributed systems › remote execution
computation migration |
0.3 | 1 | 2017 | Breaking the Boundaries in Heterogeneous-ISA Datacenters · ASPLOS 2017 |
Cloud and datacenter computing › resource management
datacenter resource management |
0.3 | 1 | 2017 | Breaking the Boundaries in Heterogeneous-ISA Datacenters · ASPLOS 2017 |
Processor architecture and microarchitecture › multiprocessor architecture
heterogeneous-ISA |
0.3 | 1 | 2017 | Breaking the Boundaries in Heterogeneous-ISA Datacenters · ASPLOS 2017 |
Systems and software security
exploitation |
0.2 | 1 | 2024 | Enforcing C/C++ Type and Scope at Runtime for Control-Flow and Data-Flow Integrity · ASPLOS (3) 2024 |
Systems and software security › exploitation
non-control data attack |
0.2 | 1 | 2024 | Enforcing C/C++ Type and Scope at Runtime for Control-Flow and Data-Flow Integrity · ASPLOS (3) 2024 |
Systems and software security › memory protection
code-pointer integrity |
0.1 | 1 | 2021 | VIP: Safeguard Value Invariant Property for Thwarting Critical Memory Corruption Attacks · CCS 2021 |
Energy-efficient computing
datacenter energy efficiency |
0.1 | 1 | 2017 | Breaking the Boundaries in Heterogeneous-ISA Datacenters · ASPLOS 2017 |
Methods — techniques the papers use, named apart from their topics
runtime type enforcement · 0.8runtime scope enforcement · 0.8system call monitoring · 0.7security policy implementation · 0.5runtime enforcement · 0.5compiler framework · 0.4OS support · 0.4
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2024 | Enforcing C/C++ Type and Scope at Runtime for Control-Flow and Data-Flow IntegrityabstractControl-flow hijacking and data-oriented attacks are becoming more sophisticated. These attacks, especially data-oriented attacks, can result in critical security threats, such as leaking an SSL key. Data-oriented attacks are hard to defend against with acceptable performance due to the sheer amount of data pointers present. The root cause of such attacks is using pointers in unintended ways; fundamentally, these attacks rely on abusing pointers to violate the original scope they were used in or the original types that they were declared as. Mohannad Ismail, Christopher Jelesnianski, Yeongjin Jang, Changwoo Min, Wenjie Xiong 0001 |
ASPLOS (3) | 2 |
| 2023 | Protect the System Call, Protect (Most of) the World with BASTIONabstractSystem calls are a critical building block in many serious security attacks, such as control-flow hijacking and privilege escalation attacks. Security-sensitive system calls (e.g., execve, mprotect), especially play a major role in completing attacks. Yet, few defense efforts focus to ensure their legitimate usage, allowing attackers to maliciously leverage system calls in attacks. Christopher Jelesnianski, Mohannad Ismail, Yeongjin Jang, Dan Williams 0001, Changwoo Min |
ASPLOS (3) | 1 |
| 2022 | Tightly Seal Your Sensitive Pointers with PACTight
Mohannad Ismail, Andrew Quach, Christopher Jelesnianski, Yeongjin Jang, Changwoo Min |
USENIX Security Symposium | 3 |
| 2021 | VIP: Safeguard Value Invariant Property for Thwarting Critical Memory Corruption AttacksabstractMost modern software attacks are rooted in memory corruption vulnerabilities, which are capable of altering security-sensitive data (e.g., function pointers) to unintended values. This paper introduces a new security property, the Value Invariant Property (VIP), and HyperSpace, our prototype that enforces VIP on security-sensitive data. HyperSpace safeguards the integrity of "data values" instead of enforcing control/data flow, allowing for low runtime overhead, yet defeating critical attacks effectively. We implement four representative security policies including Control Flow Integrity (VIP-CFI), Code Pointer Integrity (VIP-CPI), Virtual function Table protection (VIP-VTPtr), and heap metadata protection based on HyperSpace. We evaluate HyperSpace with SPEC CPU2006 benchmarks and real-world applications (NGINX and PostgreSQL) and test how HyperSpace defeats memory corruption-based attacks, including three real-world exploits and six attacks that bypass existing defenses (COOP, heap exploits, etc.). Our experimental evaluation shows that HyperSpace successfully stops all these attacks with low runtime overhead: 0.88% and 6.18% average performance overhead for VIP-CFI and VIP-CPI, respectively, and overall approximately 13.18% memory overhead with VIP-CPI in SPEC CPU2006. Mohannad Ismail, Jinwoo Yom, Christopher Jelesnianski, Yeongjin Jang, Changwoo Min |
CCS | 3 |
| 2020 | MARDU: Efficient and Scalable Code Re-randomizationabstractDefense techniques such as Data Execution Prevention (DEP) and Address Space Layout Randomization (ASLR) were role models in preventing early return-oriented programming (ROP) attacks by keeping performance and scalability in the forefront, making them widely-adopted. As code reuse attacks evolved in complexity, defenses have lost touch with pragmatic defense design to ensure security, either being narrow in scope or providing unrealistic overheads. Christopher Jelesnianski, Jinwoo Yom, Changwoo Min, Yeongjin Jang |
SYSTOR | 1 |
| 2017 | Breaking the Boundaries in Heterogeneous-ISA DatacentersabstractEnergy efficiency is one of the most important design considerations in running modern datacenters. Datacenter operating systems rely on software techniques such as execution migration to achieve energy efficiency across pools of machines. Execution migration is possible in datacenters today because they consist mainly of homogeneous-ISA machines. However, recent market trends indicate that alternate ISAs such as ARM and PowerPC are pushing into the datacenter, meaning current execution migration techniques are no longer applicable. How can execution migration be applied in future heterogeneous-ISA datacenters? Antonio Barbalace, Robert Lyerly, Christopher Jelesnianski, Anthony Carno, Ho-Ren Chuang, Vincent Legout, Binoy Ravindran |
ASPLOS | 3 |
| 2015 | Popcorn: bridging the programmability gap in heterogeneous-ISA platformsabstractThe recent possibility of integrating multiple-OS-capable, high-core-count, heterogeneous-ISA processors in the same platform poses a question: given the tight integration between system components, can a shared memory programming model be adopted, enhancing programmability? If this can be done, an enormous amount of existing code written for shared memory architectures would not have to be rewritten to use a new programming paradigm (e.g., code offloading) that is often very expensive and error prone. We propose a new software architecture that is composed of an operating system and a compiler framework to run ordinary shared memory applications, written for homogeneous machines, on OS-capable heterogeneous-ISA machines. Applications run transparently amongst different ISA processors while exploiting the most optimized instruction set for each code block. We have implemented and tested our system, called Popcorn, on a multi-core Intel Xeon machine with a PCIe Intel Xeon Phi to demonstrate the viability of our approach. Application execution on Popcorn demonstrates to be up to 52% faster than the most performant native execution on Linux, on either Xeon or Xeon Phi, while removing the burden of the programmer having to adopt a different programming model than shared memory on a heterogeneous system. When compared to an offloading programming model, Popcorn is shown to be up to 6.2 times faster. Antonio Barbalace, Marina Sadini, Saif Ansary, Christopher Jelesnianski, Akshay Ravichandran, Cagil Kendir, Alastair Murray, Binoy Ravindran |
EuroSys | 4 |