testkube-api-server-2.12.1_linux_arm64

digest	sha256:5037702622f095c0ff6b4a819e6b18cc2672ea122192a482ee69792a6163f22c
vulnerabilities
platform	linux/arm64
size	72 MB
packages	264

github.com/go-git/go-git/v6 6.0.0-alpha.4 (golang) pkg:golang/github.com/go-git/go-git/v6@6.0.0-alpha.4 # api-server.Dockerfile (36:36) COPY --from=build /app /bin/app Improper Link Resolution Before File Access ('Link Following') Affected range <=6.0.0-alpha.4 Fixed version 6.0.0-alpha.5 CVSS Score 7.1 CVSS Vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:L EPSS Score 0.292% EPSS Percentile 21st percentile Description Impact A symlink traversal issue in go-git could allow worktree operations to modify files outside the intended worktree path. The worktreeFilesystem wrapper rejected dangerous path strings, including paths containing .git, parent-directory components, or control characters. However, it did not prevent filesystem operations from following symbolic links that were already present in the worktree. As a result, a path that is safe when evaluated as a string could still resolve into the repository's Git metadata directory. For example, if s is a symbolic link to .git, writing to s/config would modify .git/config. A symbolic link at the final path component could also be followed. For example, if s points directly to .git/config, opening s for writing with truncation could overwrite the repository configuration. Exploitation requires an attacker to be able to introduce or control a symbolic link in the worktree and cause the application to perform a write through that path. Applications using storage/memory for their Storer, or go-billy/memfs for their Worktree, are not affected by this vulnerability. Patches The issue has been addressed by making the worktree filesystem wrapper a symlink-safe boundary. Worktree operations now reject paths where an existing symbolic link in any path component could cause the operation to escape the intended worktree location, including symbolic links at the final component. Users of filesystem-backed worktrees should upgrade to a patched version. Credits Thanks to @kodareef5 for reporting this issue and working with the go-git security team toward its resolution. 🥇 We would also like to thank @HughLewis20, who independently reported the same issue while a fix was already in progress. Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') Affected range <=6.0.0-alpha.4 Fixed version 6.0.0-alpha.5 CVSS Score 6.3 CVSS Vector CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:L EPSS Score 0.349% EPSS Percentile 28th percentile Description Impact A path traversal issue in go-git could allow malicious reference names to access files outside the repository's intended reference storage. Loose references are stored under .git/<reference-name>. The reference name was previously used as a path without verifying that the resolved path remained within the reference storage. A name such as refs/heads/../../config could therefore resolve to unrelated repository metadata such as .git/config or .git/HEAD. A malicious Git server could advertise such a reference name. The name may also survive refspec mapping; for example, it could be mapped to refs/remotes/origin/../../config during a clone or fetch operation. This vulnerability affects filesystem-backed repositories using the storage/filesystem package and its dotgit reference storage. Users relying exclusively on the in-memory storage implementation, storage/memory, are not affected, because reference names are not resolved as filesystem paths. Exploitation requires an application using go-git with filesystem-backed storage to interact with a malicious Git server or otherwise process attacker-controlled reference names. Patches The issue has been addressed by validating reference names at the dotgit storage entry points and rejecting names whose resolved paths could escape the reference storage. Users of filesystem-backed storage should upgrade to a patched version. Workarounds Applications that exclusively use storage/memory are not affected and do not require a workaround for this vulnerability. For applications using filesystem-backed storage, avoid cloning from or fetching from untrusted Git servers until an upgrade is possible. Applications that directly construct or process reference names may also validate them before passing them to filesystem-backed go-git storage. Application-level validation should only be considered a temporary mitigation and does not replace upgrading to a patched version. References Fixes: https://github.com/go-git/go-git/pull/2247 https://github.com/go-git/go-git/pull/2254 Credits Thanks to @Saku0512 for reporting this issue and @Sahana2524 for proposing the initial fix. 🙇

github.com/docker/cli 29.5.3+incompatible (golang) pkg:golang/github.com/docker/cli@29.5.3%2Bincompatible # api-server.Dockerfile (36:36) COPY --from=build /app /bin/app Affected range >=19.03.0+incompatible Fixed version Not Fixed EPSS Score 0.472% EPSS Percentile 38th percentile Description Docker CLI Plugins: Uncontrolled Search Path Element Leads to Local Privilege Escalation on Windows in github.com/docker/cli

golang.org/x/crypto 0.54.0 (golang) pkg:golang/golang.org/x/crypto@0.54.0 # api-server.Dockerfile (36:36) COPY --from=build /app /bin/app Affected range >=0 Fixed version Not Fixed Description The golang.org/x/crypto/openpgp package is unsafe by design, has numerous known security issues, is not maintained, and should not be used. If you are required to interoperate with OpenPGP systems and need a maintained package, consider github.com/ProtonMail/go-crypto/openpgp which is a maintained fork that aims to be a drop-in replacement for this package.

nghttp2-libs 1.69.0-r0 (apk) pkg:apk/alpine/nghttp2-libs@1.69.0-r0?arch=aarch64&distro=alpine-3.24.1&upstream=nghttp2 # api-server.Dockerfile (34:34) RUN apk --no-cache upgrade && apk --no-cache add ca-certificates libssl3 git Affected range <1.70.0-r0 Fixed version 1.70.0-r0 EPSS Score 0.263% EPSS Percentile 18th percentile Description

github.com/klauspost/compress 1.18.6 (golang) pkg:golang/github.com/klauspost/compress@1.18.6 # api-server.Dockerfile (36:36) COPY --from=build /app /bin/app Affected range >=1.16.0 <1.18.7 Fixed version 1.18.7 Description Providing a specially crafted dictionary to s2.NewDict and using it to encode data can make the encoder read out of bounds.