Skip to content
KitploitKITPLOIT
StrumentiExploitsBlog
Log in
Invia
StrumentiExploitsBlog
Invia

Strumenti di Hacking, PenTest e Cybersecurity per il tuo Arsenale di Sicurezza!

Kitploit è una directory di strumenti di hacking, cybersecurity e pentesting. Scopri gli ultimi aggiornamenti dei progetti per trovare vulnerabilità, analizzare sistemi, automatizzare i test e rafforzare la tua sicurezza.

FeedContattoPrivacy© 2026 Kitploit

Directory degli strumenti

Categorie

Vedi tutte le categorie
Loading categories
lava — LAVA: Large-scale Automated Vulnerability Addition | Kitploit
Strumenti/GitHubGitHub/panda-re/lava
Vulnerability AnalysisFuzzingBinary AnalysisPapers & ResearchLearning & Education
GitHubpanda-re/lava

lava

LAVA: Large-scale Automated Vulnerability Addition

Vedi Repository
417651181 giorno faRevisionato da Kitploit

Più Popolari

Vedi tutti →

Scopri gli strumenti più utilizzati dalla nostra community.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 Il toolkit OSINT definitivo: grafo di indagine, punteggio di affidabilità, famiglie di alias, mappa, timeline e report. 49 moduli, oltre 400 siti, nessuna chiave API richiesta.

    906
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    # App di esecuzione con un tocco GhostLock (CVE-2026-43499)

    725
  • 3

    looking-glass

    anonghosty/looking-glass

    Piattaforma CSIRT che importa i report di Shadowserver in MongoDB e li riproduce come mappe interattive, analisi, risultati, avvisi e dashboard executive.

    442
  • 4

    wifit3

    derv82/wifit3

    Wifite ma solo USB e multipiattaforma.

    434
  • 5

    jumpserver

    jumpserver/jumpserver

    JumpServer è una piattaforma open-source di gestione degli accessi privilegiati (PAM) che fornisce ai team DevOps e IT un accesso sicuro e on-demand a endpoint SSH, RDP, Kubernetes, database e RemoteApp tramite un browser web.

    412
  • 6

    SafeLine

    chaitin/safeline

    WAF self-hosted e reverse proxy che filtra il traffico HTTP malevolo, blocca SQL injection, XSS e attacchi bot, con limitazione del tasso e crittografia dinamica HTML/JS.

    360

Esplora tutti gli strumenti

Sfoglia la nostra collezione di strumenti

Vedi tutti gli strumenti →
Condividi
Contenuto non disponibile nella lingua richiesta. Visualizzazione della versione inglese.
# LAVA: Large Scale Automated Vulnerability Addition

[![Publish Lava Package and Container](https://raw.githubusercontent.com/panda-re/actions/workflows/publish_docker.yml/badge.svg)](../../actions/workflows/publish_docker.yml)

[![Lava Tests](https://raw.githubusercontent.com/panda-re/actions/workflows/parallel_tests.yml/badge.svg)](../../actions/workflows/parallel_tests.yml)

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](https://hub.docker.com/r/pandare/lava). 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:

```bash
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:

```bash
/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`):

```bash
/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:

```bash
/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:

```bash
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](https://github.com/panda-re/lava/blob/master/install.sh) 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](https://github.com/panda-re/lava/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](https://github.com/panda-re/lava/blob/master/python/src/pyroclastic/utils/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](https://github.com/panda-re/lava/blob/master/scripts/setup_postgres.sh) 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:

```bash
./scripts/dump_database.sh toy_andrew toy_andrew.dump
./scripts/import_database.sh toy_andrew.dump toy_andrew_restored
```

Pass actual PostgreSQL database names, including the `db_suffix` from
`host.json` where applicable (for example, `toy_andrew_ubuntu`). These scripts
use `POSTGRES_USER` and `POSTGRES_PASSWORD`, with standard PostgreSQL variables
(`PGHOST`, `PGPORT`, `PGUSER`, `PGPASSWORD`) taking precedence. Host and port
default to `localhost:5432`; PostgreSQL's password file also works. Credentials
must be exported in the shell; the scripts do not load `.env` automatically.

The dump script refuses to overwrite an archive and publishes it only after
`pg_dump` succeeds. Import creates a new database and refuses an existing name.
Restore runs in one transaction, with objects owned by the restoring user and
original ownership and grants omitted. If restore fails, the new empty database
remains for inspection. A successful import exercises the backup's restoration.
Use PostgreSQL client tools matching the source server's major version, and
restore to the same or a newer supported server version.

Keep matching source code, inputs, configuration, and generated files separately;
database archives do not contain external files. Restoring does not translate
mined results to a different source target. Configure LAVA's resolved `db` name
to use the restored database for subsequent injection experiments.

### PostgreSQL in a container (Podman on Linux)

If you cannot install PostgreSQL on the host, run it in a separate rootless
Podman container. For ease of setup, use host networking for both PostgreSQL
and LAVA; no `podman network create` or port publishing (`-p`) is needed.

In your workspace (for example, `~/lava`), create a `.env` containing
`POSTGRES_USER=lava` and `POSTGRES_PASSWORD=your-database-password`, using plain
`KEY=value` lines without shell `export` statements or surrounding quotes.
Keep this file out of version control. From that directory, run:

```bash
chmod 600 .env
podman volume create lava-pgdata
podman run -d --name lava-postgres \
  --network host --shm-size=1g \
  --env-file .env -e POSTGRES_DB=postgres \
  -v lava-pgdata:/var/lib/postgresql/data \
  docker.io/library/postgres:17 \
  -c listen_addresses=127.0.0.1
podman logs lava-postgres
```

Wait for the log to report that the database is ready to accept connections.
The `-d` option runs PostgreSQL in the background: you can run LAVA from the
same shell, with no second terminal needed. Stop and restart the existing
database container with `podman stop lava-postgres` and
`podman start lava-postgres`; do not repeat `podman run` to restart it.
Detached operation does not configure startup after a reboot or guarantee
survival of a lab's logout cleanup policy.

Run the LAVA container with `--network host --env-file .env` too, and set
`"host": "127.0.0.1"` and `"port": 5432` in `host.json`. Port 5432 must be free
on the host; if necessary, add `-c port=5433` to the PostgreSQL command and use
5433 in `host.json`. PostgreSQL listens only on host loopback, although other
users on the same server can reach that port and must authenticate.

Host networking does not expose host files. Bind-mount the LAVA workspace,
target data, and PANDA cache into the LAVA container at the same absolute paths
used in your configurations, with appropriate write permissions. Use the launcher with Podman (it preserves your host UID/GID for mounted files):

```bash
scripts/docker-shell.sh --runtime podman --env-file .env lava-init
scripts/docker-shell.sh --runtime podman --env-file .env
```

The second command opens an interactive LAVA shell. Host networking is the
default; use `--network NAME` if you prefer a shared container network. Exported
host credentials override values from `--env-file` when both are provided.

The named volume persists database files independently of the container. Large
databases still consume real host disk space: check your quota and Podman's
storage location (`podman info --format '{{.Store.GraphRoot}}'`) before large
experiments, and budget for indexes, WAL, temporary files, and backups. Use an
approved persistent data location if home storage is too small; a volume is
not a backup. The image's user/password variables initialize an empty volume
only; changing `.env` later does not change existing database credentials.
Keep the PostgreSQL major version pinned; changing it requires a database
upgrade procedure. See the [official PostgreSQL image documentation](https://hub.docker.com/_/postgres)
and [Podman run reference](https://docs.podman.io/en/latest/markdown/podman-run.1.html).

# Usage

Finally, you can run `lava` to actually inject bugs into a program. 
Just provide the name of a project that is in the `target_configs` directory, for example:

```
lava -ak toy
```

You should now have a buggy copy of toy!

If you want to inject bugs into a new target, you will likely need to make some
modifications. Check out [How-to-Lava](https://github.com/panda-re/lava/blob/master/docs/how-to-lava.md) for guidance.

# Documentation
Check out the [docs](https://github.com/panda-re/lava/blob/master/docs/) folder to get started.

# Authors

LAVA is the result of several years of development by many people; a
partial (alphabetical) list of contributors is below:

* Andy Davis
* Brendan Dolan-Gavitt
* Andrew Fasano
* Zhenghao Hu
* Patrick Hulin
* Amy Jiang
* Engin Kirda
* Tim Leek
* Andrea Mambretti
* Andrew Quijano
* Wil Robertson
* Aaron Sedlacek
* Rahul Sridhar
* Frederick Ulrich
* Ryan Whelan
Scarica lo strumento