Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/ispras/casr/llms.txt

Use this file to discover all available pages before exploring further.

CASR ships as a set of compiled binaries with no runtime interpreter required. You can get up and running in minutes by downloading a prebuilt release archive, installing from crates.io, or compiling from source for maximum control. Choose the method that best fits your environment.
macOS support is currently experimental. GDB-dependent features (casr-gdb, severity estimation via the exploitable engine) may not work correctly on macOS. Linux is the fully supported platform.

​
Prerequisites

​
Runtime Dependencies

CASR requires GDB at runtime for stack-trace collection and lsb-release to record OS metadata inside reports. 
sudo apt install gdb lsb-release

​
Build Dependencies

Required only when building from source or installing via cargo install. 
sudo apt install build-essential clang

​
Rust Toolchain

CASR is written in Rust. Install Rust via rustup or update an existing installation: 
# Install
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh

# Or update an existing installation
rustup update

​
Installation Methods

​
Install from crates.io

The simplest way to install the latest stable release. The casr crate on crates.io includes all CLI tools except casr-dojo.
cargo install casr
To include casr-dojo (for uploading reports to DefectDojo), enable the dojo feature flag:
cargo install -F dojo casr
Cargo places binaries in ~/.cargo/bin/. Make sure this directory is on your $PATH before running any casr-* command.

​
Docker Usage

CASR is commonly run inside Docker containers as part of automated fuzzing pipelines. Because CASR disables address randomization (ASLR) and uses ptrace to run GDB, Docker containers need elevated capabilities.
Always start your CASR container with --cap-add=SYS_PTRACE --security-opt seccomp=unconfined. Without these flags, casr-gdb will fail and severity estimation via the exploitable engine will be unreliable.
docker run --rm \
  --cap-add=SYS_PTRACE \
  --security-opt seccomp=unconfined \
  -v "$(pwd)/crashes:/crashes" \
  -v "$(pwd)/reports:/reports" \
  my-casr-image \
  casr-san -o /reports/report.casrep -- /crashes/test_binary

​
Verify Installation

After installation, confirm that the core binaries are available and show the expected version: 
casr-san --version
All three commands should print casr-<tool> 2.13.1 (or the version you installed). If a command is not found, ensure ~/.cargo/bin or /usr/local/bin is on your $PATH.

​
Next Steps

Quickstart

Generate your first crash report and run the full triage pipeline in minutes.

Introduction

Learn about CASR’s architecture, supported languages, and available tools.

Build docs developers (and LLMs) love

Get started for freeTalk to us