build(deps): refresh the pinned base image digests - #140
Merged
Conversation
Clears the four open Trivy alerts on the API image (two systemd CVEs, each reported twice): a local privilege escalation via systemd-homed, and an unprivileged local user being able to terminate arbitrary processes. Both are Debian packages inside the base image, not application code. The scan runs with ignore-unfixed, so anything it reports has a patch available — these were waiting on nothing but a digest refresh. Pinning by digest is what makes the base auditable (review finding M10), and the cost of that is exactly this: the pin has to be moved deliberately when the upstream image is rebuilt. sdk:10.0 e1fc6e42… -> e1ffd2a9… aspnet:10.0 207cc514… -> a4556ed0… Both taken from mcr.microsoft.com today, the way the comment at the top of the file describes. Container build & scan runs on this path, so its own Trivy step is the check on whether this actually cleared them. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019h7znwAftvs36vD4YwKMRf
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Clears the four open Trivy alerts on the API image — two systemd CVEs, each reported twice (a local privilege escalation via
systemd-homed, and an unprivileged local user being able to terminate arbitrary processes). Both live in Debian packages inside the base image, not in application code.Why they were open, and why this is the whole fix
The scan runs with
ignore-unfixed: true, so anything it reports has a patch available. These were waiting on nothing but a digest refresh — Microsoft had already rebuilt the images.They didn't fail CI because the gate is
severity: CRITICAL,HIGHand these are MEDIUM. That's the design working as intended: the gate blocks on what's urgent, the Security tab shows what's coming. It just needs someone to act on the tab.Pinning by digest is what makes the base auditable (review finding M10). The cost of that is exactly this — a tag would have picked the rebuild up silently, a digest has to be moved deliberately.
Both read from
mcr.microsoft.comtoday, the way the comment at the top ofDockerfile.apidescribes.Verification
Container build & scanruns on theDockerfile.apipath, so its own Trivy step on this PR is the check on whether this actually cleared them — and it uploads SARIF either way. Merging re-scansmainand closes the alerts.Also
dapperpinned the identical digests, so it carried the identical exposure with no alerts raised against it. Same one-line change: #141.🤖 Generated with Claude Code
https://claude.ai/code/session_019h7znwAftvs36vD4YwKMRf
Generated by Claude Code