Global ETD Search

Search theses and dissertations gathered from participating repositories worldwide. Every result links back to the library that holds it. No account is needed.

Results

Showing 1 to 20 of 98 for “"Memory Safety"”.

  1. Gradual Memory Safety

    … extends the theory of Gradual Types to include memory safe Region-Types and Region-Based Memory Management. It also makes advancements in the capabilities of Region-Based systems. Lastly, it presents the Svejk language and Hasek Type System.

    nmu Repository record for Gradual Memory Safety (opens in a new tab)

  2. Hardware-assisted memory safety

    … As a result, computer systems are plagued by memory vulnerabilities. Many remedies exist; from defensive programming techniques to memory-safe languages. But these approaches require security-expertise and costly porting of existing code. To achieve wide-spread use, we must integrate security …

    aalto Repository record for Hardware-assisted memory safety (opens in a new tab)

  3. Asynchronous hardware-enforced memory safety

    Memory corruption attacks, such as buffer overflow attacks, have been threatening software security for more than three decades. Despite tremendous efforts by developers and researchers to prevent programs written in memory-unsafe language (e.g., C/C++) from memory errors (the root cause of memory …

    uiuc Repository record for Asynchronous hardware-enforced memory safety (opens in a new tab)

  4. Hardware-based Always-On Memory Safety

    In computer systems, memory safety violations have been a persistent problem. Recent industry reports show that memory safety vulnerabilities addressed in their products still account for over 70% of the entire security cases. With the severity of the problem, securing computer systems against it …

    gatech Repository record for Hardware-based Always-On Memory Safety (opens in a new tab)

  5. Memory Safety Through Branded Type Inference

    Memory safety is a major concern in software development. Languages such as Rust allow for memory safety without sacrificing performance, by performing analysis at compile time. However, this complicates the process of writing software, and some minor performance sacrifices still remain in certain …

    oregon Repository record for Memory Safety Through Branded Type Inference (opens in a new tab)

  6. Selective Pointer Metadata Inlining for Efficient Memory Safety Enforcement

    Memory safety is a persistent concern in software engineering, particularly in C/C++ programs, due to their manual memory management and lack of built-in bounds checking. While safe languages like Java and Rust mitigate these issues by design, rewriting legacy C/C++ applications is often …

    toronto-retro Repository record for Selective Pointer Metadata Inlining for Efficient Memory Safety Enforcement (opens in a new tab)

  7. Runtime Enforcement of Memory Safety for the C Programming Language

    Memory access violations are a leading source of unreliability in C programs. Although the low-level features of the C programming language, like unchecked pointer arithmetic and explicit memory management, make it a desirable language for many programming tasks, their use often results in …

    maryland Repository record for Runtime Enforcement of Memory Safety for the C Programming Language (opens in a new tab)

  8. Hardware-Software Co-Designed GPU Security Mechanism for Memory Safety

    Memory safety has long been a critical challenge in low-level programming languages such as C and C++. Similar concerns have recently emerged in GPU programming, which relies on C/C++-style languages and now plays a vital role in critical systems such as autonomous driving and medical diagnostics. …

    gatech Repository record for Hardware-Software Co-Designed GPU Security Mechanism for Memory Safety (opens in a new tab)

  9. Memory Safety Acceleration on RISC-V for C Programming Language

    Memory corruption vulnerabilities can lead to memory attacks. Three of the top ten most dangerous weaknesses in computer security are memory-related. Memory attack is one of a computer system’s oldest but everlasting problems. Companies and the government lost billions of dollars due to memory …

    unsw Repository record for Memory Safety Acceleration on RISC-V for C Programming Language (opens in a new tab)

  10. Týr : a dependent type based code transformation for spatial memory safety in LLVM

    … C programming language does not enforce spatial memory safety: it does not ensure that memory accessed through a pointer to an object, such as an array, actually belongs to that object. Rather, the programmer is responsible for keeping track of allocations and bounds information and ensuring that …

    brazil-ufrgs Repository record for Týr : a dependent type based code transformation for spatial memory safety in LLVM (opens in a new tab)

  11. Checking Memory Safety of Level 1 Safety-Critical Java Programs using Static-Analysis without Annotations

    Safety-Critical Java (SCJ) has been designed specifically to ring performance and reliability to the development of safety-critical Java programs. SCJ introduces a novel programming paradigm based on missions and handlers, and has been designed to ease certification. One of the distinguishing …

    whiterose Download PDF for Checking Memory Safety of Level 1 Safety-Critical Java Programs using Static-Analysis without Annotations (opens in a new tab)

  12. Designing Practical Software Bug Detectors Using Commodity Hardware and Common Programming Patterns

    … of three approaches using data race bugs, memory safety bugs, and permission check bugs, respectively. First, we leverage the commodity hardware transactional memory (HTM) selectively to use the dynamic data race detector only if necessary, thereby reducing the overhead from 11.68x to …

    vt Repository record for Designing Practical Software Bug Detectors Using Commodity Hardware and Common Programming Patterns (opens in a new tab)

  13. A Methodology For Micro-Policies

    … tagging that include forms of access control, memory safety, compartmentalization, and information-flow control. Our methodology is based on a symbolic machine that extends a conventional RISC-like architecture with tags. Tags express security properties of parts of the program state ("this is …

    penn Repository record for A Methodology For Micro-Policies (opens in a new tab)

  14. A Functional Approach to Memory-Safe Operating Systems

    … languages--with static type systems and dynamic memory management using garbage collection--are a known tool for helping programmers to reduce the number of memory errors in programs. By using such languages, we can establish correctness properties relating to memory-safety through our choice of …

    portland-state Repository record for A Functional Approach to Memory-Safe Operating Systems (opens in a new tab)

  15. FUSE: Single-Pass Binary Co-Instrumentation for Accurate Vulnerability Detection

    … without source code remains vulnerable to memory safety er- rors that compilers detect via AddressSanitizer (ASAN). Existing binary-level ASAN tools rely on heuristic disassembly that fails on complex programs and produces false positives. We present FUSE, a static binary instrumentation …

    vt Repository record for FUSE: Single-Pass Binary Co-Instrumentation for Accurate Vulnerability Detection (opens in a new tab)

  16. Cache Design and Analysis for Mitigating Hardware Security in Multicore Systems

    … Furthermore, Spectre and Meltdown have reshaped memory safety. Historically, memory safety issues were attributed to software bugs and human errors, leading software security experts to develop defenses such as bound checking and sandboxing. However, it is crucial to recognize that transient …

    tamu Repository record for Cache Design and Analysis for Mitigating Hardware Security in Multicore Systems (opens in a new tab)

  17. Implementing SoftBound on Binary Executables

    Though languages like C and C++ are known to be memory unsafe, they are still used widely in industry because of their memory management features, low level nature and performance benefits. Also, as most of the systems software has been written using these languages, replacing them with memory safe …

    ku Repository record for Implementing SoftBound on Binary Executables (opens in a new tab)

  18. SHAPES: easy and high-level memory layouts

    … they will need to consider how to place data in memory so as to exploit spatial locality and achieve high memory bandwidth. Performing such manual memory optimisations usually sacrifices readability, maintainability, memory safety, and object abstraction. This is further exacerbated in managed …

    greece Repository record for SHAPES: easy and high-level memory layouts (opens in a new tab)

  19. Modern C++ and Rust in embedded memory-constrained systems

    … advantages such as low runtime overhead and good memory management, despite their memory safety issues. In an attempt to overcome the safety issues, many high level languages have been introduced recently, albeit with a high execution time overhead. This thesis mainly focuses on Modern C++ and …

    chalmers Repository record for Modern C++ and Rust in embedded memory-constrained systems (opens in a new tab)

  20. Diverse partial memory replication

    … program diversity called Diverse Partial Memory Replication (DPMR), aimed at detecting memory safety errors. DPMR is an automatic compiler transformation that replicates some subset of an executable's data memory and applies one or more diversity transformations to the replica. DPMR can …

    uiuc Repository record for Diverse partial memory replication (opens in a new tab)

Page 1 of 5