Join our Newsletter — 33% off our NHI Course

Who is exposed when CVSS misses the shipped artifact?

 

(@nhi-mgmt-group)
Member Moderator
Joined: 2 years ago
Posts: 20225
Topic starter  

TL;DR: CVE closure depends on proof that the fix reached the shipped artifact, not just the source repository, according to Finite State. Firmware and fielded devices need binary verification and supplier evidence to avoid false closure and prove the release actually changed.

Editorial analysis by NHI Mgmt Group, based on content published by Finite State: “CVE Remediation for Devices You've Already Shipped”.

Key questions

Q: How should teams prioritise vulnerabilities when CVSS scores conflict with real-world exploitability?

A: Treat CVSS as a baseline, then re-rank findings using exploit intelligence, asset criticality, and internet exposure.

Q: What should security teams do first when a vulnerable service cannot be safely patched yet?

A: Start with a runtime mitigation that blocks the observed exploit path, not a broad rule that assumes every instance of the CVE behaves the same.

Q: What breaks when a CVE is patched in source but not in the shipped artifact?

A: The remediation claim breaks, because the vulnerable code can still be present in the release image even when source control shows a fix.

Practitioner guidance

  • Verify the shipped artifact, not just the source tree Compare the vulnerable build and the fixed build at the binary level, then confirm the corrected code is present in the release image customers actually run.
  • Separate patching from remediation decisions Classify each finding as patch, reconfiguration, compensating control, component replacement, or written risk acceptance so the closure path is explicit.
  • Prioritise by reachability and exploitation evidence Use reachability checks, active exploitation status, and product exposure to rank findings ahead of raw severity scores.

Bottom line: CVE closure depends on proof that the fix reached the shipped artifact, not just the source repository.

Glossary terms: CVE remediation, Artifact Verification, Reachability Assessment, Risk Acceptance

Explore further

View Full Forum →  |  NHI Foundation Course →  |  Our Services →  |  Read the full analysis →


This topic was modified 1 week ago by NHI Mgmt Group

   
Quote
(@mr-nhi)
Member Moderator
Joined: 6 months ago
Posts: 20715
 

Artifact verification is the real control boundary in remediation. Once a product ships, closure depends on proving the fix exists in the built image, not in the repository. That changes vulnerability management from a ticketing exercise into a release-integrity problem, especially for firmware and supplier-built components. Practitioners need evidence at the binary layer before they can claim remediation is complete.

A few things that frame the scale:

  • The average time to mitigate a leaked secret is 36 hours, highlighting the operational burden of manual remediation processes, according to the 2024 State of Secrets Management Survey.
  • The average estimated time to remediate a leaked secret is 27 days, despite 75% of organisations expressing strong confidence in their secrets management capabilities, according to the State of Secrets in AppSec.

A question worth separating out:

Q: Why do firmware teams need build verification before closing a vulnerability?

A: Because the build step can reintroduce, omit, or alter the fix after code review has passed. Cached objects, stale linked libraries, and packaging errors all produce a release that looks patched on paper but is still vulnerable in production. Verification at the artifact layer is what converts a fix into evidence.

👉 Read our full editorial: CVE remediation fails when the fix never reaches the shipped artifact


This post was modified 1 week ago by NHI Mgmt Group

   
ReplyQuote
Share:

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.