Skip to content

Add base-image freshness check to the CVE scan runbook#190

Merged
lex57ukr merged 1 commit into
mainfrom
sop-check-base-image-on-cve
Jul 6, 2026
Merged

Add base-image freshness check to the CVE scan runbook#190
lex57ukr merged 1 commit into
mainfrom
sop-check-base-image-on-cve

Conversation

@lex57ukr

@lex57ukr lex57ukr commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

Summary

When triaging a ci-tools CVE, a newer base image often clears base-layer and apt CVEs in a batch, but the Vulnerability Scan Failure Runbook only mentioned bumping the base for CVEs already attributed to the base layer. This adds an explicit early step to check for a fresher base digest before hand-patching — it's frequently the cheapest fix, and Dependabot's weekly base bump may lag a freshly-disclosed CVE.

Changes

  • Add a "check for a fresher base image first" step to the Vulnerability Scan Failure Runbook in docs/how-to/publish-image.md, noting a base bump needs no tool refresh (the pinned tools are independent of the base digest).

Further Comments

Docs-only follow-up from the ci-tools CVE / Lua 5.4 work (#189). make lint-md clean.

When triaging a CVE, check for a newer base digest before hand-patching:
base-layer and apt CVEs usually clear in a batch on a rebuilt base, and a
base bump needs no tool refresh here (tools are pinned independently of the
base). Dependabot's weekly bump may lag a fresh CVE, so this is the cheapest
first thing to try.
@lex57ukr lex57ukr added the documentation Improvements or additions to documentation label Jul 6, 2026
@lex57ukr
lex57ukr merged commit ee2c0de into main Jul 6, 2026
9 checks passed
@lex57ukr
lex57ukr deleted the sop-check-base-image-on-cve branch July 6, 2026 02:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant