Skip to content

Releases

v0.5.0: hardened against hostile images, fuzz tests, container image

Choose a tag to compare

@depuschm depuschm released this 28 Oct 06:20
9a5ec18

Upgrade recommended. Up to v0.4.0, a crafted container image could mislead the scanner:

  • a file named like node<TAB>.node could make a vulnerable node binary show as PATCHED;
  • in image and --rootfs scans, crafted file names and symlinks could make the scanner read files from the machine it ran on.

Both are fixed. File names with control characters are now reported as REVIEW instead of being parsed, and nothing outside the scanned filesystem is read. The problems were found by the project's new fuzz tests.

New

  • Container image ghcr.io/depuschm/brotli-k8s-scan:0.5.0 (x86-64 and arm64): no base image, runs as an unprivileged user, signed build provenance.
  • Kubernetes Job: deploy/job.yaml runs the scan from inside the cluster with its own service account and minimal RBAC.
  • Fuzz tests on every change; ShellCheck at every severity; a guide for contributors.

Verify

gh attestation verify brotli-k8s-scan.sh --repo depuschm/brotli-k8s-scan
gh attestation verify oci://ghcr.io/depuschm/brotli-k8s-scan:0.5.0 --repo depuschm/brotli-k8s-scan

Full list: CHANGELOG.md

v0.4.0 – honest Envoy verdicts, real-cluster tests, signature files on releases

Choose a tag to compare

@depuschm depuschm released this 27 Oct 21:32
57558f4

What changed since v0.3.0:

Scanner

  • Envoy: official Envoy builds keep no Brotli error table, so its version decides. The default cluster mode runs envoy --version in the pod; image and --no-exec scans now report Envoy as REVIEW with an explanation instead of a generic "stripped binary" note. The README's Envoy and Istio rows are corrected (Istio: not tested).
  • Clearer exec errors: when a pod has no shell, the report now says why (e.g. exec: "sh": executable file not found).

Evidence and trust

  • Tested against the official Bun 1.4.3 / 1.4.4 and Envoy 1.36.11 / 1.36.12 release binaries.
  • Real Kubernetes cluster test in CI (kind): real kubectl exec into BusyBox pods, --no-exec with real crane pulls by digest, --image with real docker.
  • This release attaches its signed provenance as files: brotli-k8s-scan.sigstore.json and brotli-k8s-scan.intoto.jsonl.
  • CodeQL on every change, hash-pinned test dependencies, Dependabot, a weekly uncached test run, OpenSSF Scorecard.

Download and verify

curl -fsSLO https://github.com/depuschm/brotli-k8s-scan/releases/download/v0.4.0/brotli-k8s-scan.sh
curl -fsSLO https://github.com/depuschm/brotli-k8s-scan/releases/download/v0.4.0/SHA256SUMS
curl -fsSLO https://github.com/depuschm/brotli-k8s-scan/releases/download/v0.4.0/brotli-k8s-scan.sigstore.json
sha256sum -c SHA256SUMS --ignore-missing
gh attestation verify brotli-k8s-scan.sh --repo depuschm/brotli-k8s-scan --bundle brotli-k8s-scan.sigstore.json

Full changes: CHANGELOG.md

v0.3.0 – first release: find vulnerable Brotli (CVE-2026-111497) by checking the binary

Choose a tag to compare

@depuschm depuschm released this 27 Oct 20:12
34d8a03

First public release of brotli-k8s-scan: find vulnerable Brotli decoders (CVE-2026-111497, a.k.a. Broccoli2Shell / Node2Shell / HTTP2Shell) in Kubernetes clusters, container images and Linux hosts.

Version numbers lie. Node.js 22.23.4 still reports Brotli "1.1.0", and Ubuntu's fixed libbrotli1 1.1.0-2ubuntu0.1 is still "1.1.0". Besides version checks, this tool looks inside the binary: the fix added the decoder error code _ERROR_FORMAT_BLOCK_SWITCH, so it also finds bundled copies in Node.js, Bun, Python wheels, Pillow, .NET and Envoy, and recognises distro backports. How it works

Highlights

  • Cluster scan via kubectl exec (one container per image), or --no-exec (pulls images by digest; needs only list-pods permission)
  • --image / --images-from for container images, --rootfs / for a Linux host
  • .NET: shared runtimes and self-contained apps; runtimes built against the system libbrotli are judged by that library
  • report.json, --sarif for GitHub code scanning, YARA rules with the same fingerprint
  • --print-probe shows exactly what runs in your containers, --dry-run shows what would be touched
  • Tested on x86-64 and arm64 against real vulnerable and fixed builds (Brotli, Node.js, Python, Ubuntu, Microsoft .NET); tests run without network

Download and verify

curl -fsSLO https://github.com/depuschm/brotli-k8s-scan/releases/download/v0.3.0/brotli-k8s-scan.sh
curl -fsSLO https://github.com/depuschm/brotli-k8s-scan/releases/download/v0.3.0/SHA256SUMS
sha256sum -c SHA256SUMS --ignore-missing
gh attestation verify brotli-k8s-scan.sh --repo depuschm/brotli-k8s-scan

Full changes: CHANGELOG.md