Skip to content
crunchtoolsPublic

About

Fleet CVE scanner: runs grype over the crunchtools image fleet on a schedule and writes a status file the Nagios check reads (RT #1551).

Resources

Stars

0 stars

Watchers

0 watching

Forks

Repository files navigation

grype

Scheduled CVE scanner for the crunchtools image fleet — the runtime replacement for the per-repo build-time Trivy gate (RT #1551).

pip-audit already catches Python dependency CVEs at build time. What nothing watched was base-image / OS-package CVEs on the published images, and the rebuild drift that freezes an image weeks behind its errata. Quay's own Clair scanner returns unsupported for our public repos, so there is no registry verdict to read — this image runs grype itself and writes a status file the Nagios check judges.

How it works

Kagetora (every 6h) ──starts──▶ grype.crunchtools.com.service (oneshot)
                                      │  cve-scan
                                      │  • grype db update   (DB on a volume)
                                      │  • scan each fleet image (local store
                                      │    first, registry fallback)
                                      │  • classify: severity + fix.state + rce
                                      ▼
                                 cve.status  ──read──▶ nagios-agent
                                                       check_image_cve.sh
                                                       OK / WARNING / CRITICAL

The scanner calls no model and makes no decisions — it counts; the Nagios check routes. Routing (deterministic, so no model wakes to triage):

Finding Verdict Action
unfixable only (no upstream fix) OK nothing — .trivyignore owns these
stale, or a fixable High WARNING rebuild within 6h
a fixable Critical CRITICAL page, and rebuild
DB older than 48h, missing file, image absent UNKNOWN notify

Two verbs, one image

  • cve-scan — the detector above. Holds no write credential.
  • rebuilder (later) — acts on findings (files Rebuild tickets, dispatches builds). Runs as its own unit with its own credentials; a scanner that can read images should not also hold a token that can write.

cve.status format

CVE generated=<epoch> db_built=<epoch> db_age_days=<n> db_updated=<0|1> images=<n> elapsed=<s>
CVE item=<ref> seen=<epoch> result=ok source=<podman|registry> total=.. crit=.. high=.. med=.. fix_crit=.. fix_high=.. unfix=.. rce=..
CVE item=<ref> seen=<epoch> result=error msg=<text>
CVE end=1

db_built is the DB's real build date, not the scan time: a failed refresh leaves it old on purpose so the check catches a stale scanner. An image that cannot be scanned is result=error, never dropped.

Development

tests/test_classify.sh          # classifier unit tests (bash + jq, no grype)
podman build -f Containerfile .  # build the image

The fleet list is fleet-images.conf; on gloval the unit mounts the host's authoritative list over it. Licensed AGPL-3.0-or-later.

Deployment notes (gloval)

The oneshot (deploy/systemd/grype.crunchtools.com.service) is started by a 6h Hermes job on Kagetora (no host .timer), pinned to a release tag with no auto-update, exactly like the deployer.

  • /tmp must be a disk volume, never --tmpfs. grype's podman: provider exports the image being scanned into /tmp; on a memory-backed tmpfs that export counts against the container's memory cgroup, and a ~1 GB image OOM-kills the scan even at an 8 GB limit. A disk-backed /tmp volume drops the peak to ~1.3 GB (one scan holds the vuln DB in memory), so 4 GB is comfortable.
  • cve.status is shared through /var/lib/grype-scan, statically labelled container_file_t with no MCS category (semanage fcontext + restorecon, mirroring /var/lib/deployer) and mounted with no :z/:Z by both this oneshot (rw) and the nagios-agent container (ro). ExecStartPost restorecon re-asserts that label on the output every run.
  • The nagios-agent check reads cve.status with STATUS=/var/lib/grype-scan/cve.status set on its nrpe command.

About

Fleet CVE scanner: runs grype over the crunchtools image fleet on a schedule and writes a status file the Nagios check reads (RT #1551).

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages