Building 70 Projects ranging from beginner to advanced so anyone can β learn from, build upon, use as a reference, or even copy directly. Owned by my cybersecurity company π
Go aicertificationcloud-engineeringcybercybersecuritycybersecurity-analystcybersecurity-certificationcybersecurity-certificationscybersecurity-educationcybersecurity-jobscybersecurity-portfoliocybersecurity-projectscybersecurity-toolsgrchackinglearningpentestingproject-repositoryprojetcspython
docs(lisdex): the README did not look like any of the other projects'
CarterPerez-deve686c47c6d3c
diff --git a/PROJECTS/advanced/zero-day-vulnerability-scanner/README.md b/PROJECTS/advanced/zero-day-vulnerability-scanner/README.mdindex d79b0de0..9cc5a0a3 100644--- a/PROJECTS/advanced/zero-day-vulnerability-scanner/README.md+++ b/PROJECTS/advanced/zero-day-vulnerability-scanner/README.md@@ -1,13 +1,31 @@-# lisdex+<!-- Β©AngelaMos | 2026 -->+<!-- README.md -->++```json+βββ ββββββββββββββββββ βββββββββββ βββ+βββ βββββββββββββββββββββββββββββββββββ+βββ ββββββββββββββ βββββββββ ββββββ+βββ ββββββββββββββ βββββββββ ββββββ+βββββββββββββββββββββββββββββββββββββββ βββ+ββββββββββββββββββββββββββ βββββββββββ βββ+```-Point-and-run zero-day scanner for C and C++ parsers. Give it a source tree, get-back distinct bugs with severities and a disclosure-ready reproducer.+[](https://github.com/CarterPerez-dev/Cybersecurity-Projects/tree/main/PROJECTS/advanced/zero-day-vulnerability-scanner)+[](https://www.rust-lang.org)+[](#the-optional-booster)+[](https://github.com/AFLplusplus/AFLplusplus)+[](https://hexhive.epfl.ch/magma/)+[](https://www.gnu.org/licenses/agpl-3.0)-No API key. No account. No cloud. Everything runs locally.+> A keyless memory-corruption scanner for C and C++ parsers in Rust. Point it at a source tree and it ranks which functions actually parse untrusted bytes, writes a fuzz harness for the best one with no model in the loop, builds the library under AddressSanitizer without a hand-written build script, runs an AFL++ campaign, then collapses the crash pile into distinct bugs with a stack-hash key, hand-labelled severity, a minimized reproducer proven to still trigger the same bug, and a coordinated-disclosure advisory in human and machine form. It needs no API key, no account and no cloud, and every stage refuses out loud rather than guessing.-```sh-curl -fsSL https://angelamos.com/lisdex/install.sh | bash-```+## Why the parsers keep failing++Memory corruption in file-format and media parsers is the CVE class that refuses to die. These libraries are old C, they run on bytes an attacker fully controls, and they sit underneath everything: an image decoder is reachable from a browser tab, a chat app, a thumbnailer and a mail client at the same time. CVE-2023-4863, a heap buffer overflow in libwebp's Huffman decoder, was exploited in the wild and forced emergency out-of-band patches across Chrome, Firefox, Android and Electron in September 2023, because a single parser is a shared dependency of half the internet. Stagefright did the same to Android in 2015 through the media parser, reachable by MMS.++Fuzzing is how these get found, and fuzzing itself is a solved commodity. AFL++ is free, fast and excellent. The expensive parts are the two on either side of it. Somebody has to decide which of nine hundred exported functions takes attacker bytes and write a harness that drives it correctly, and somebody has to turn the resulting pile of thousands of crash files into the handful of distinct bugs it actually represents, with a reproducer a maintainer will accept. Both are hand work, both need someone who already knows the library, and both are why most C projects have no fuzz target at all.++lisdex automates the two ends and drives AFL++ in the middle. It is validated against [Magma](https://hexhive.epfl.ch/magma/), a benchmark of real historical CVEs re-planted into real libraries with canaries that report which specific bug a crash reached, so "it found something" can be checked against ground truth rather than asserted.## What it does@@ -19,7 +37,15 @@ source tree -> entry points -> harness -> instrumented build -> campaignA real campaign against libpng: **182 crash files, 2 distinct bugs**. Gettingfrom the first number to the second is most of what this tool is for.-## Use it+## Quick Start++```bash+curl -fsSL https://angelamos.com/lisdex/install.sh | bash+```++One command, zero further steps: it installs the Rust toolchain and AFL++ if they+are missing, builds lisdex, drops it on your `PATH`, and leaves `lisdex` runnable+by name. No API key, no account, no cloud. Then point it at a tree:```sh# what in this tree parses untrusted bytes?diff --git a/PROJECTS/advanced/zero-day-vulnerability-scanner/justfile b/PROJECTS/advanced/zero-day-vulnerability-scanner/justfileindex c94569c1..a63a65e0 100644--- a/PROJECTS/advanced/zero-day-vulnerability-scanner/justfile+++ b/PROJECTS/advanced/zero-day-vulnerability-scanner/justfile@@ -135,7 +135,7 @@ m10-gate-reset:# One-way mirror of this project into the standalone repo install.sh clones.# This tree stays canonical; the mirror is a copy. docs/ is dev-only and never ships.-publish target="~/dev/lisdex":+publish target="~/dev/CURRENT/lisdex":@test -d {{target}} || { echo "no checkout at {{target}} - clone [email protected]:CarterPerez-dev/lisdex.git there first"; exit 1; }rsync -a --delete \--exclude='.git/' \