Skip to content
KitploitKITPLOIT
ИнструментыЭксплойтыБлог
Log in
Отправить
ИнструментыЭксплойтыБлог
Отправить

Инструменты для хакинга, пентеста и кибербезопасности — ваш арсенал защиты!

Kitploit — это каталог инструментов для хакинга, кибербезопасности и пентестинга. Находите последние обновления проектов для поиска уязвимостей, анализа систем, автоматизации тестирования и усиления вашей безопасности.

ЛентыКонтактыКонфиденциальность© 2026 Kitploit

Каталог инструментов

Категории

Все категории
Loading categories
lava — LAVA: Large-scale Automated Vulnerability Addition | Kitploit
Инструменты/GitHubGitHub/panda-re/lava
Vulnerability AnalysisFuzzingBinary AnalysisPapers & ResearchLearning & Education
GitHubpanda-re/lava

lava

LAVA: Large-scale Automated Vulnerability Addition

Репозиторий
417651184 дней назадПроверено Kitploit
Поделиться
Контент недоступен на запрошенном языке. Показываем английскую версию.

LAVA: Large Scale Automated Vulnerability Addition

Publish Lava Package and Container

Lava Tests

Evaluating and improving bug-finding tools is currently difficult due to a shortage of ground truth corpora (i.e., software that has known bugs with triggering inputs). LAVA attempts to solve this problem by automatically injecting bugs into software. Every LAVA bug is accompanied by an input that triggers it whereas normal inputs are extremely unlikely to do so. These vulnerabilities are synthetic but, we argue, still realistic, in the sense that they are embedded deep within programs and are triggered by real inputs. Our work forms the basis of an approach for generating large ground-truth vulnerability corpora on demand, enabling rigorous tool evaluation and providing a high-quality target for tool developers.

LAVA is the product of a collaboration between MIT Lincoln Laboratory, NYU, and Northeastern University.

Quick Start

Docker

The latest version of LAVA's master branch is automatically built as a docker images based on Ubuntu 22.04 and published to Docker Hub. Most users will want to use the lava container which has PANDA and LAVA installed along with their runtime dependencies, but no build artifacts or source code to reduce the size of the container.

To use the lava container you can pull it from Docker Hub:

$ docker pull pandare/lava

Or build from this repository:

$ DOCKER_BUILDKIT=1 docker build -t pandare/lava:local .

If Docker Engine runs directly inside WSL and build steps cannot access the network (for example, APT reports Temporary failure resolving), try using WSL's host network for the build:

DOCKER_BUILDKIT=1 docker build --network=host -t pandare/lava:local .

This applies to build steps only; containers launched later use their own network settings.

Container workspace

From a workspace containing target_bins/ and target_configs/, use the launcher to open a shell or run a command. It mounts the workspace at the same absolute path so paths written to host.json remain valid between runs. Replace /path/to/lava with the checkout containing the launcher:

/path/to/lava/scripts/docker-shell.sh
/path/to/lava/scripts/docker-shell.sh lava-init
/path/to/lava/scripts/docker-shell.sh lava --help

Docker runs as your UID/GID with your host HOME path and always mounts ~/.panda/ at that same path in the container. Existing QCOWs and kernel files are reused, and downloads and cache changes persist there. The launcher creates ~/.panda/ if needed. The launcher uses pandare/lava:latest by default; use --image pandare/lava:v3.3.4 to select a release, or --image pandare/lava:local for the local build above.

PostgreSQL must already be running. Export POSTGRES_USER and POSTGRES_PASSWORD. The launcher defaults to Docker host networking. On Linux, this lets LAVA reach PostgreSQL on the host machine; keep "host": "localhost" and set "port" to PostgreSQL's listening port in host.json (for example, 5433):

/path/to/lava/scripts/docker-shell.sh lava -ak toy

Override the default with --network NETWORK for a database container on a shared Docker network. Use its container name as "host" and its internal PostgreSQL port (usually 5432). Once configured:

/path/to/lava/scripts/docker-shell.sh --network NETWORK lava -ak toy

-k deletes existing project data without confirmation. The launcher replaces the old project-name-first interface. Put launcher options before the command; the -- separator remains supported but is optional.

HPC with Apptainer / Singularity

On an allocated compute node, use the runtime provided by the cluster. Pull a versioned image once into persistent storage, then reuse it for jobs:

apptainer pull /path/to/scratch/lava-v3.3.4.sif docker://pandare/lava:v3.3.4
/path/to/lava/scripts/docker-shell.sh --runtime apptainer \
  --image /path/to/scratch/lava-v3.3.4.sif lava-init
/path/to/lava/scripts/docker-shell.sh --runtime apptainer \
  --image /path/to/scratch/lava-v3.3.4.sif lava -tc toy

Use --runtime singularity if that is the installed command. These runtimes use the host user's identity and network; configure host.json for a reachable PostgreSQL service and export the same credentials. The launcher neither starts the database nor requests a scheduler allocation. Run it inside your cluster's interactive allocation or batch script. This does not establish that a release image supports the complete pipeline; verify the image installation and run a toy project before submitting a large mining job.

Ubuntu, Debian

Local Installation

On a system running Ubuntu 22.04, you should be able to just run bash install.sh. Note that this install script will install packages and make changes to your system. You can remove the binaries using sudo apt-get remove lava.

Once you finish installing the binary, then you can install locally running pip install ..

NOTE that the Python package requires a SQL file generated from compiling the binaries that is placed into python/src/pyroclastic/data/lava.sql. Without this file, the Python package will not work correctly.

Regular installation

Alternatively, you can manually install LAVA's dependencies and then build from source. Download the Debian packages located in the releases. Then install the python package pip install pyroclastic.

Final steps

Utilizing host.json

Next, run init-host to generate a host.json in your current working directory directory. This file is used by LAVA to store settings specific to your machine. You can edit these settings as necessary, but the default values should work, see vars.py.

A few values to keep in mind are the following:

  • host is the name of the Postgres SQL database with all the LAVA bugs. Currently, it defaults to database, although if you installed LAVA locally, you likely should change this to localhost

NOTE: You also need two environment variables for the Postgres SQL database:

  • POSTGRES_PASSWORD This is the password for the Postgres SQL user
  • POSTGRES_USER This is the Postgres SQL username

Project configurations

Project configurations are located in the target_configs directory, where every configuration is located at target_configs/projectname/projectname.json. Paths specified within these configuration files are relative to values set in your host.json file.

Setting up postgres SQL database

As alluded to, you should create a Postgres SQL user. You can use a script to using the environment variables for the following:

  • Create the user with provided username and password from environment variables.
  • Update Postgres SQL database on host to accept traffic from external sources (e. g. LAVA Docker container)

Database backup and restore

Use PostgreSQL's full custom-format archive to preserve the mined database's schema, rows, IDs, relationships, and sequence values. The diagnostic table printer is not a backup. After mining finishes, run:

./scripts/dump_database.sh toy_andrew toy_andrew.dump
./scripts/import_database.sh toy_andrew.dump toy_andrew_restored
Скачать инструмент

Популярное

Смотреть все →

Откройте для себя самые используемые инструменты нашего сообщества.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 Полный набор инструментов OSINT: граф расследования, оценка достоверности, семейства псевдонимов, карта, временная шкала и отчёты. 49 модулей, более 400 сайтов, API-ключи не требуются.

    732
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    # Приложение GhostLock с запуском в один клик (CVE-2026-43499)

    506
  • 3

    ARTEX

    baarai/artex

    Платформа автономного тестирования на проникновение на основе мультиагентной LLM с агентами-планировщиками и агентами-исполнителями, графами активов и исследования, записью MITM-трафика и повторной проверкой уязвимостей.

    405
  • 4

    redforge

    cybersecurity91/redforge

    Браузерный инструментарий для red team с 102 офлайн-инструментами для разведки, генерации полезной нагрузки, атак на учётные данные, криптографии, кодирования и отчётности по проектам.

    342
  • 5

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    Система действий для кибербезопасности на базе ИИ — где намерение превращается в управляемое исполнение, доказательства становятся оперативной памятью, а каждая операция улучшает следующую.

    261
  • 6

    antifox

    antifox-ai/antifox

    Мультиагентная платформа автономного тестирования на проникновение на базе ИИ, которая выполняет разведку, обнаружение поверхности атаки, валидацию эксплуатации и подготовку отчётов с подтверждающими доказательствами.

    259

Изучить все инструменты

Просмотрите нашу коллекцию инструментов

Смотреть все инструменты →