build(deps): refresh the pinned base image digests - #141
Merged
Conversation
Same two systemd CVEs as on main: 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. This branch pinned the identical digests, so it carried the identical exposure — it simply had no alerts raised against it. The scan runs with ignore-unfixed, so anything it reports has a patch available; these were waiting on nothing but a digest refresh. sdk:10.0 e1fc6e42… -> e1ffd2a9… aspnet:10.0 207cc514… -> a4556ed0… 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.
The
dapperhalf of #140.This branch pinned the identical base image digests as
main, so it carried the identical exposure — two systemd CVEs in Debian packages inside the image (a local privilege escalation viasystemd-homed, and an unprivileged local user being able to terminate arbitrary processes). No alerts were raised against it; the Security tab view that surfaced them was filtered tobranch:main.The scan runs with
ignore-unfixed: true, so anything it reports has a patch available. These were waiting on nothing but a digest refresh.Verification
Container build & scanruns onpull_requestagainstdapperand on theDockerfile.apipush path, so its Trivy step on this PR is the check.🤖 Generated with Claude Code
https://claude.ai/code/session_019h7znwAftvs36vD4YwKMRf
Generated by Claude Code