nmatt0/mithril

IoT static scanner for secrets, SBOM, CVEs and more.

mithril analyzes the contents of firmware and IoT software, whether a single file or an unpacked rootfs. It looks for embedded secrets and keys, a software bill of materials (SBOM), known CVEs affecting those components, open-source licenses, boot-security posture (U-Boot env, device tree, FIT/AVB/UEFI verified boot), and weak or leaked public keys (keys whose private half is public, ROCA, undersized RSA). It reports each finding with its evidence and a confidence, and it speaks clean JSON so scripts and LLM agents can drive it as easily as people can.

A scan makes no network calls. Secrets, SBOM, and license analysis are fully offline, and the CVE pass reads a local vulnerability mirror you refresh out of band.

mithril is the semantic companion to moria, which identifies and unpacks firmware. moria maps the bytes. mithril reads the contents.

moria -e firmware.bin            # identify + unpack  -> firmware.bin.extracted/
mithril firmware.bin.extracted/  # secrets + SBOM + CVEs + licenses

It has no build-time dependency on moria. Point it at any file or directory.

• Firmware-aware SBOM. Beyond package databases (dpkg/opkg/apk/rpm), it recovers components from ELF version banners, versioned libc filenames, and the kernel banner, so it finds openssl/busybox/uClibc even in a stripped image with no package manager. Emitted as CycloneDX and SPDX.
• CVEs it owns end to end. A local OSV + NVD/CPE mirror plus a curated, version- and kconfig-gated kernel-CVE checklist (high-signal, not exhaustive: an empty kernel result means none of the curated set is in range, not that the kernel is clean). Every match records how sure it is (exact version vs affected range vs CPE), stays release-precise where /etc/os-release allows, and is annotated with CISA KEV and EPSS.
• Honest by construction. Secrets ride a deterministic offline ladder: pattern (shape), then structural (a parsed JWT or PEM key), then validated (a recomputed checksum, such as GitHub tokens and crypt hashes). mithril asserts well-formed, never "live," and an empty result is a real answer rather than a tool failure.
• Weak and leaked keys, proven offline. For every public key it recovers (certs, SSH host/authorized keys, embedded keys) it checks whether the private half is obtainable: a fingerprint match against a compiled-in corpus of hardcoded/default keys whose private half is public (rapid7 ssh-badkeys, the Vagrant insecure key), the ROCA fingerprint (CVE-2017-15361), undersized/broken RSA, and factoring recoveries that hand you a factor outright (Fermat close primes, batch-GCD shared primes across the image, Wiener small-d) via a small in-tree bignum. A hit means impersonation, login, or forgery, not just a weak cipher suite.
• Fully offline and reproducible. No network at scan time; the CVE mirror is refreshed by an explicit, separate step. Air-gappable.
• Safe on hostile input. Untrusted bytes go through one bounds-checked reader. Parsers degrade to a clean error rather than crash, and the CVE index is memory-mapped so a scan never parses the whole thing.

cmake -S . -B build -DCMAKE_BUILD_TYPE=Release
cmake --build build -j
cmake --install build --prefix ~/.local     # or /usr/local (needs sudo)

No third-party libraries. The install step places the mithril binary; a bare cp build/mithril ~/.local/bin works just as well. Debug with sanitizers: cmake -S . -B build -DMT_SANITIZE=ON.

Output is human-readable by default. Pass -j for JSON.

mithril <file|dir>            # run every pass (human-readable)
mithril -j <dir>              # JSON, for tools and agents
mithril --secrets <dir>       # secrets only
mithril --sbom -C out/ <dir>  # SBOM only -> out/sbom.cdx.json + out/sbom.spdx.json
mithril --cve <dir>           # match components against the local mirror (offline)
mithril --cve --kernel-cves-all <dir>  # also list every kernel.org CVE for the kernel version (opt-in)
mithril --cve --component-cves-all <dir>  # human view: list every component CVE, not just high-signal (opt-in)
mithril --licenses <dir>      # licenses only
mithril --license-paths <dir> # licenses, with each license's file locations listed
mithril --boot <dir>          # boot-security intel: U-Boot env, device tree, FIT/AVB, UEFI Secure Boot
mithril --boot bios.bin       # UEFI Secure Boot posture from a raw AMI/EDK2 BIOS (docs/boot-security.md)
mithril --keys <dir>          # public-key weakness: leaked/default keys, ROCA, weak RSA, factoring
mithril --rules my.json <dir> # add user-defined rules (docs/user-rules.md)
mithril --fetch-db            # FIRST RUN: download the CVE mirror (a networked command)
mithril --fetch-db --with-kernel-feed  # also fetch the optional full kernel.org CVE feed
mithril --update-db           # rebuild the CVE mirror from source (a networked command)
mithril --help

First run: the --cve pass needs a local vulnerability mirror, so run mithril --fetch-db once before your first CVE scan (details under The CVE mirror). Without it, --cve reports the missing DB and exits nonzero. Secrets, SBOM, and licenses are fully offline and need no setup.

Naming any of --secrets / --sbom / --cve / --licenses / --boot / --keys runs just those. Naming none runs them all.

--cve reads a local mirror under ~/.local/share/mithril/ (honors $MITHRIL_DB), a compact, memory-mapped index built from OSV.dev, the NVD 2.0 API, the CISA KEV catalog, and FIRST's EPSS scores that a scan loads in a fraction of a second. Get it two ways, and only these two commands ever touch the network:

• mithril --fetch-db downloads a prebuilt index (rebuilt weekly) and verifies every file against a published SHA-256 before installing. It does no upstream scraping: it just fetches the finished index. Needs curl. Point it at a mirror with $MITHRIL_DB_URL.
• mithril --update-db rebuilds the index from the upstream feeds yourself. Slower, needs curl and unzip, and is the authoritative path if you want to control exactly what goes in. Set $NVD_API_KEY to raise the NVD rate limit (optional; it works without one, just slower).

Add --with-kernel-feed to either command to also get the optional full kernel.org (Linux CNA) CVE feed that backs --kernel-cves-all. By default the kernel is triaged by a curated high-signal checklist; --kernel-cves-all lists every kernel.org CVE for the detected version instead, matched branch-aware (a bug fixed in 6.6.17 is reported for 6.6.10 but not 6.6.110). It is a separate asset so the base mirror stays lean; building it needs tar.

Build it once either way; every scan after that is offline. See docs/cve-join.md and docs/cve-index-format.md.

• secrets: credential and key material in file content (cloud keys, tokens, JWTs, private keys, high-entropy KEY=… values). /etc/shadow and htpasswd hashes are classified with weak-algorithm and empty-password flags, and credential/crypto/config files are flagged by path.
• sbom: components and versions from package databases, language manifests, binary version strings, libc filenames, and the kernel banner, keyed on purl (with CPE co-derived), emitted as CycloneDX and SPDX.
• cve: the SBOM joined against the local OSV + NVD/CPE mirror, plus the curated kernel-CVE checklist, annotated with KEV and EPSS. The default human view shows only foothold-worthy component CVEs (on CISA KEV, or Critical, or a hard High/Critical floor of CVSS >= 7.0 with EPSS traction, low attack complexity, and real impact or a trending remote DoS), sorted worst-first; it drops Mediums, local DoS, and the high-complexity crypto class. --component-cves-all lists them all. JSON always carries the complete set plus a component_cve_scan summary.
• licenses: SPDX identification from SPDX-License-Identifier tags and LICENSE/COPYING/NOTICE text. Human output summarizes by id and count; --license-paths lists each license's file locations, and JSON always carries the full paths array.

File-type identification, extraction, and embedded key/certificate file signatures are moria's job; mithril reads content, it does not unpack. How discovery works is documented in docs/engine-design.md.

MIT, see LICENSE. The vulnerability and license data fetched by --update-db (OSV.dev, NVD, CISA KEV, FIRST EPSS, and the kernel.org Linux CNA feed) belong to their respective sources. mithril mirrors them locally and does not redistribute them.