Repository navigation
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
π Security & Privacy | π Major | β‘ Quick win
π§© Analysis chain
π Script executed:
Repository: openshift-hyperfleet/hyperfleet-sentinel
Length of output: 222
π Script executed:
Repository: openshift-hyperfleet/hyperfleet-sentinel
Length of output: 2564
π Script executed (no clone):
Length of output: 698
π Script executed (no clone):
Length of output: 2567
π Web query:
registry.access.redhat.com ubi9/go-toolset 9.8-1786351949 manifest digestπ‘ Result:
The manifest digest for a specific container image tag like registry.access.redhat.com/ubi9/go-toolset:9.8-1786351949 is not a single, universally static value because these tags are updated frequently by Red Hat as part of their security patching and maintenance cycle [1][2][3]. To obtain the current manifest digest for this specific image tag, you should use one of the following authoritative methods: 1. Red Hat Ecosystem Catalog: Visit the official Red Hat Ecosystem Catalog page for the UBI 9 Go Toolset [4]. This site provides the official manifest list digest for the current version of the image, which ensures you pull the correct, supported image for your architecture [4]. 2. Skopeo: Use the skopeo tool to inspect the image remotely without pulling it to your local system [5]. This command will return the digest associated with the tag: skopeo inspect docker://registry.access.redhat.com/ubi9/go-toolset:9.8-1786351949 3. Docker/Podman: You can also identify the digest after pulling the image by running: podman images --digests --no-trunc or docker images --digests --no-trunc Because Red Hat container tags are mutable and updated regularly, referencing them by tag rather than digest may lead to pulling different image content over time [6][7]. It is a recommended best practice to verify the specific digest for your environment at the time of your build using the methods above [6].
Citations:
Pin both container base images by digest before merge.
Line 3 resolves to manifest-list digest
sha256:0b471eb04868f3d9d90bf3c668f9c6c7a22cef07474ac9fec067909dfd7dec7c:FROM registry.access.redhat.com/ubi9/go-toolset:9.8-1786351949@sha256:0b471eb04868f3d9d90bf3c668f9c6c7a22cef07474ac9fec067909dfd7dec7c AS builderPin the runtime default
BASE_IMAGEat line 1 as well. Tag-only references permit different image contents across builds, creating a supply-chain integrity risk under CWE-494.π€ Prompt for AI Agents
Source: Path instructions