gnutls: add GnuProject source_provenance (un-dark the vuln scan, surfaces CVE-2025-32988)#258
gnutls: add GnuProject source_provenance (un-dark the vuln scan, surfaces CVE-2025-32988)#258bryan-minimal wants to merge 1 commit into
Conversation
gnutls had no source_provenance, so the vuln scanner emitted no query for it and reported 0/0/0 — despite a real HIGH (CVE-2025-32988) affecting the pinned 3.8.9. GnuProject → pkg:generic/gnu/gnutls resolves via the existing cpe_remap to NVD's gnu:gnutls, so the scan now correctly flags it. Verified locally: `pkgmgr vulns --package gnutls` now reports CVE-2025-32988 (HIGH); the upstream version check still resolves cleanly (up-to-date at 3.8.9 — the fix is in the unreleased 3.8.10, so this is a track-until-fix-ships HIGH with no bump yet). First of the dark-package provenance backfill (66-package audit, wf w4kghqujr). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
Warning Review limit reached
More reviews will be available in 1 hour, 32 minutes, and 23 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
What
Adds
source_provenance = GnuProject "gnutls"to gnutls'sbuild.ncl.Why
gnutls was one of the 66 "dark" packages — no
source_provenance, so the vuln scanner never queried it and reported 0/0/0. It's actually sitting on a HIGH:CVE-2025-32988affects the pinned 3.8.9.GnuProject "gnutls"→pkg:generic/gnu/gnutls, which resolves via the existingcpe_remap(gnu:gnutls) — so no supply-chain change is needed, the scan path (pm#193) lights up immediately.Verified locally
pkgmgr vulns --package gnutls→ now reports CVE-2025-32988 (HIGH) (was 0/0/0).pkgmgr check --package gnutls→ still resolves cleanly (up-to-date at 3.8.9). Note: the fix is in the unreleased 3.8.10, so there's no bump available yet — this is a track-until-fix-ships HIGH, surfaced now instead of hidden.First of the dark-package provenance backfill from the 66-package audit (wf w4kghqujr). mesa + dnsutils follow (those also need a
cpe_remaprow in supply-chain).🤖 Generated with Claude Code