Skip to content

security: distrust compromised eMudhra intermediates - #1

Merged
battman21 merged 6 commits into
mainfrom
cursor/emudhra-ca-trust-store-0692
Oct 22, 2026
Merged

battman21 merged 6 commits into
mainfrom
cursor/emudhra-ca-trust-store-0692

Conversation

@battman21

@battman21 battman21 commented Oct 22, 2026 •

Copy link
Copy Markdown
Owner

Summary

Removes the compromised eMudhra intermediates from the live trust path and brings every live component up to the 22 Oct 2026 advisory baseline. Requirements are floors (caret ranges, >=, floating image tags, and the stable Rust channel) with build-time checks. Exact pins remain only in archived campaign evidence under research/showdown/evidence/.

Certificate trust

  • rustls-webpki 0.103.16, webpki-roots 1.0.10, rustls 0.23.46 (CVE-2026-111943 / RUSTSEC-2026-0382).
  • Yanked chacha20 0.10.1 is 0.10.2. Showdown quinn-proto is 0.11.19.
  • An in-memory rustls test accepts a leaf from a trusted CA and rejects the same leaf presented to a client that trusts a different CA.

Baseline floors

  • Rust channel is stable. rust-version is 1.96.1. CI rejects a rustc older than 1.96.1.
  • Go module is go 1.26.10 with toolchain go1.27.3. CI rejects an older toolchain and runs govulncheck.
  • Node engines and scripts/check-node-floor.mjs accept 22.23.4, 24.22.1, or 26.12.1. CI uses Node 24.x with check-latest so the runner cache cannot keep 24.22.0, plus engine-strict and npm audit --audit-level=high.
  • Python CI uses 3.14 with check-latest, requires 3.13.17 or newer, and upgrades pip>=26.2.2 and certifi>=2026.10.19.
  • Campaign cryptography moved from ==49.0.0 to >=50.0.0.
  • All 14 showdown images use rust:1.99-trixie and debian:trixie-slim, run apt-get upgrade, and fail the build unless rustc is at least 1.96.1 and ca-certificates is at least 20250419+deb13u1. Each image curls https://example.com during the build.
  • The v33 image now copies replay_v01.rs and depends on libc and tempfile, so the current source builds.
  • Showdown hickory-resolver 0.26.1 is 0.26.3.

PHP, Java, Composer, Next.js, React, python-jose, Starlette, Pillow, and PyJWT are not dependencies of this repository.

Local verification

  • cargo test --workspace --locked --all-targets -- --include-ignored passed, including the Postgres graph test, the Supabase RLS test against PostgreSQL 16.15, and the untrusted-chain test.
  • cargo clippy --workspace --all-targets --locked -- -D warnings, cargo fmt --all --check, cargo test --doc, and cargo build --workspace --locked --bins passed.
  • Go 1.27.3 go test ./... passed. Python 3.14.9 conformance passed (4 tests). Node 24.22.1 npm test passed (15 tests). The Node floor script also passed on 22.23.4.
  • All 14 images built with docker build --pull --no-cache and smoked with curl https://example.com.

Scanner results and the component table are in the "Advisory baseline coverage" comments. CI on f172ccc is green: rust and conformance both passed with the stable Rust channel and the rustc >= 1.96.1 floor check. The pull request is ready for review and is not merged.

Open in Web Open in Cursor 

cursoragent and others added 4 commits October 22, 2026 08:06
Bump rustls-webpki to 0.103.16 and webpki-roots to 1.0.10 so
certificate verification rejects the guessable eMudhra keys
(CVE-2026-111943, RUSTSEC-2026-0382). Install Debian
ca-certificates 20250419~deb12u2 in showdown image builders and
pin CI Node.js to 22.23.4.

Co-authored-by: Owen <battman21@users.noreply.github.com>
Move rustls to 0.23.46, the yanked chacha20 0.10.1 crate to 0.10.2,
and showdown's quinn-proto to 0.11.19. These are compatible official
releases for the remaining cargo audit findings.

Co-authored-by: Owen <battman21@users.noreply.github.com>
Replace the exact Node and Debian CA pins with minimum floors, and
replace Cargo exact pins with caret ranges. Update the workspace and
campaign lockfiles to the latest compatible releases, including
jsonwebtoken 11 and p256 0.14, and reject an untrusted TLS chain.

Co-authored-by: Owen <battman21@users.noreply.github.com>
Raise live toolchains and images to the 22 Oct 2026 advisory baseline: rustc 1.99.1 with an MSRV floor of 1.96.1, Go 1.26.10 built with 1.27.3, Node 24.x with an engines floor, Python 3.14 with pip and certifi floors, Debian trixie campaign images, and cryptography >= 50.0.0. Clear the showdown hickory-resolver high and make the v33 image build the current replay source.

Co-authored-by: Owen <battman21@users.noreply.github.com>
@cursor

cursor Bot commented Oct 22, 2026

Copy link
Copy Markdown

Advisory baseline coverage

Checked every live component against the 22 Oct 2026 advisory baseline. Floors are minimums. The installed or resolved release is the current one where the lockfile or image could be updated. Commit c3731b6.

Component Before After Floor Status
rustc channel 1.92.0 channel 1.99.1, rust-version 1.96.1 >= 1.96.1 (latest 1.99.1) meets
rustls 0.23.46 0.23.46 >= 0.23.46 meets
rustls-webpki 0.103.16 0.103.16 >= 0.103.16 meets
webpki-roots 1.0.10 1.0.10 >= 1.0.10 meets
ring 0.17.14 0.17.14 latest 0.17.14 meets
chacha20 0.10.2 0.10.2 unyanked 0.10.2 meets
quinn-proto (showdown) 0.11.19 0.11.19 >= 0.11.18 meets
hickory-resolver (showdown) 0.26.1 0.26.3 >= 0.26.2 meets
tokio (workspace) 1.54.1 1.54.1 >= 1.44.2 meets
tokio (showdown lock) 1.53.1 1.53.1 >= 1.44.2 (latest 1.54.1) meets floor; full cargo update blocked by missing olx-core
hyper (showdown) 1.11.0 1.11.0 latest 1.12.0, no window advisory below latest; not high
Go 1.23 go 1.26.10, toolchain go1.27.3 1.26.10 / 1.27.3 meets
klauspost/cpuid v2.0.12 v2.4.1 current meets
golang.org/x/sys absent 0.49.0 (indirect) only if x/net or x/crypto is used meets; neither is a dependency
Node CI 22.x, check >= 22.23.4 24.x, engines plus scripts/check-node-floor.mjs 22.23.4 / 24.22.1 / 26.12.1 meets
@noble/hashes ^2.4.0 ^2.4.0 no named floor meets; npm audit clean
typescript ^7.0.2 ^7.0.2 no named floor meets
Python CI system 3.12.3 setup-python 3.14, check >= 3.13.17 3.14.9 or 3.13.17 meets; local run was 3.14.9
pip system CI pip>=26.2.2 >= 26.2.2 meets; local 26.2.2
certifi not declared CI certifi>=2026.10.19 >= 2026.10.19 meets; local 2026.10.19
cryptography ==49.0.0 >=50.0.0 (resolved 50.0.2) >= 50.0.0 meets
campaign images rust:1.92-bookworm plus digest, debian:bookworm-slim rust:1.99-trixie, debian:trixie-slim, apt-get upgrade trixie or Alpine 3.22–3.24 built and smoked; 47 unfixed HIGH remain
ca-certificates exact 20250419~deb12u2 floating, build check >= 20250419+deb13u1 trixie 20250419+deb13u1 enforced in every image build
next, react-server-dom, sharp, undici, axios, vite, Astro not dependencies not dependencies named floors n/a
PHP, Composer, Java not dependencies not dependencies PHP 8.5.12 / 8.4.27 n/a
python-jose, starlette, anyio, Pillow, PyJWT not dependencies not dependencies remove jose; other named floors n/a
PostgreSQL (local tests) 16.15 16.15 16.15 meets
Docker Engine (this VM) 29.1.3 29.1.3 >= 29.9.2 environment is below the floor; not vendored
research/showdown/evidence/ exact pins and old lockfiles unchanged not a live build input left as campaign records; filesystem scan had 0 high

Scanners

  • osv-scanner 2.7.0: the first scan reported HIGH on showdown hickory-resolver 0.26.1 (GHSA-5j98-2g5x-46v6, GHSA-6w6g-hm98-mhgm). After the surgical bump to 0.26.3 the scan is clean of High and Critical.
  • npm audit (--omit=dev --audit-level=high) in conformance/typescript: 0 vulnerabilities.
  • pip-audit 2.10.1 on research/showdown/requirements-v70.txt with cryptography 50.0.2: no known vulnerabilities.
  • govulncheck on conformance/go with Go 1.27.3: no vulnerabilities.
  • cargo audit --deny warnings: workspace lockfile exit 0. research/showdown/docker/build-v33/Cargo.lock exit 0 after adding libc and tempfile. Live campaign lockfiles were already clean.
  • composer audit: no composer.json. Not applicable.
  • trivy 0.76.1 filesystem (--severity HIGH,CRITICAL, evidence and target skipped): exit 0 after the hickory bump.
  • trivy image on all 14 tags (v13–v19, v33–v35, v40–v43): 47 HIGH, 0 CRITICAL, and 0 with a fixed version. Packages are bsdutils, curl, libacl1, libblkid1, libcurl4t64, liblastlog2-2, libmount1, libsmartcols1, libsystemd0, libtinfo6, libudev1, libuuid1, login, mount, ncurses-base, ncurses-bin, perl-base (fix_deferred), and util-linux. Each image already runs apt-get upgrade. Debian trixie has no fixed version for these. They stay open.

Tests and smoke

  • cargo clippy --workspace --all-targets --locked -- -D warnings: pass (1.99 clippy chunks_exact_to_as_chunks fixed with as_chunks).
  • cargo test --workspace --locked --all-targets -- --include-ignored: pass. Includes the ignored Postgres graph test, the Supabase RLS test on local PostgreSQL 16.15, and the untrusted TLS chain test.
  • cargo test --workspace --locked --doc: pass. cargo build --workspace --locked --bins: pass (ndabi_registry_v01, ndabi_registry_postgres_v01, ndabi_registry_mongodb_v01). cargo fmt --all --check: pass.
  • Go 1.27.3 go test ./...: pass. Python 3.14.9 conformance/test_vectors.py: 4 tests OK. Node 24.22.1 npm test: 15 pass. Floor script also passed on Node 22.23.4.
  • docker build --pull --no-cache and docker run --rm --entrypoint curl … https://example.com: BUILD_OK and SMOKE_OK for all 14 tags. v33 needed replay_v01, libc, and tempfile before that source built.
  • Showdown unit tests are not in CI. A local run reported 252 tests and 4 pre-existing FileNotFoundErrors for missing process-00.json files under v32, v33, v40, and v41. The showdown crate itself was not compiled: it path-depends on onlife_v2/crates/olx-core, which is not in this checkout.

@battman21
battman21 marked this pull request as ready for review October 22, 2026 10:17
cursoragent and others added 2 commits October 22, 2026 10:22
setup-node was reusing the runner cache at 24.22.0, below the 24.22.1 floor. Ask setup-node and setup-python to resolve the latest release that matches the floating range.

Co-authored-by: Owen <battman21@users.noreply.github.com>
rust-toolchain.toml named rustc 1.99.1 exactly. Use the stable channel and keep the CI check that rustc is at least 1.96.1.

Co-authored-by: Owen <battman21@users.noreply.github.com>
@cursor

cursor Bot commented Oct 22, 2026

Copy link
Copy Markdown

Advisory baseline coverage

Update for f172ccc. rust-toolchain.toml no longer pins rustc to 1.99.1.

Component Before After Floor Status
rustc exact channel 1.99.1 channel stable, rust-version 1.96.1 >= 1.96.1, enforced by the existing CI dpkg --compare-versions check meets

The rest of the earlier coverage table is unchanged. CI for f172ccc is running.

@cursor

cursor Bot commented Oct 22, 2026

Copy link
Copy Markdown

Advisory baseline coverage

CI on f172ccc is green. rust and conformance both passed with channel stable and the existing rustc >= 1.96.1 floor check. The rustc row in the previous coverage comment stands.

@battman21
battman21 merged commit 650875a into main Oct 22, 2026
2 checks passed
@battman21
battman21 deleted the cursor/emudhra-ca-trust-store-0692 branch October 23, 2026 22:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants