Chainguard

Use of the backend-facing $scheme variable in the trailing-slash directory redirect in nginx.conf of Chainguard Academy (edu) from commit 0b75ff98057f69b044a3e7194e428066ac5ad0d4 before commit 93dc0e50739c225f5aee2e803800a47fc0feb906 allows an on-path network attacker to read or modify documentation content served to a victim via an HTTPS request for a slashless directory path, because TLS terminates at the load balancer in front of Nginx and the resulting 301 response redirects the client to a plaintext http:// URL. Browsers that ship the HSTS preload list are not affected, because the .dev top-level domain is preloaded; clients that do not enforce HSTS, such as command-line HTTP clients and scripts that follow redirects, are affected.

**Name of the Vulnerable Software and Affected Versions** Chainguard Academy (edu) integrate-platform-docs composite GitHub Action versions from commit 7375a80caabcc31c33ec90f29687ed78c13d16ff through commit fb0efb2537d326ab18c07d620875b8ed2a4b39f3 **Description** Improper neutralization of special elements used in an OS command allows an actor who controls the `project id` or `storage bucket` inputs to execute arbitrary shell commands on the GitHub Actions runner. This occurs because these inputs are interpolated directly into Bash gcloud storage cp commands in several steps via `${{ inputs.* }}` expressions. **Recommendations** Update the integrate-platform-docs composite GitHub Action to commit fb0efb2537d326ab18c07d620875b8ed2a4b39f3.

**Name of the Vulnerable Software and Affected Versions** apko versions 0.2.0 through 1.4.4 **Description** The software allows users to build and publish OCI container images from apk packages. A flaw exists in the `UserEntry.Parse` and `GroupEntry.Parse` functions within `pkg/passwd` when reading UID and GID fields from `/etc/passwd` and `/etc/group` entries. The system uses `strconv.Atoi` to convert these fields to `uint32` without performing a range check. On 64-bit platforms, negative values wrap and out-of-range values, such as 4294967296 (2^32), are truncated to 0. An attacker controlling a package installed into the image can provide an entry that appears to be an unprivileged UID or GID but is written into the final image as UID 0 or GID 0 (root). This truncated UID is also utilized when resolving the image's run-as user. **Recommendations** Update to version 1.4.5.