Vulnerabilidades / GHSA-wfqx-gjrf-g28r

crítica

GHSA-wfqx-gjrf-g28r

Crossplane: Signature verification TOCTOU allows installing unverified package content via mutable tag

Publicada Modificada
En la Trivy database desde, como mínimo, el 24 oct 2026, 07:11 UTCNo consta cuándo entró antes de ese build.

Severidad por fuente

GHSA9.1CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H

La etiqueta propia de Trivy es CRITICAL. Crítica según GHSA.

Descripción

## Summary Crossplane allows package signature verification to be configured via the `ImageConfig` mechanism. When enabled, the package manager uses cosign to verify that packages are correctly signed before pulling and installing them. When a package is installed using a tag reference (e.g., a semantic version), a malicious OCI registry could serve a correctly signed image for verification, then subsequently serve an unsigned image for installation. This is possible because Crossplane resolves the tag reference separately for each step. This vulnerability is relevant only for users who do all three of the following: 1. Configure signature verification for packages, 2. Install packages using tag references rather than digests, and 3. Install packages from registries they do not control. ## Mitigation Installing packages by image digest rather than using tags avoids this issue. ## Fix The package manager has been updated to resolve tag references once and use the resulting digest for both signature verification and image fetching. This ensures that Crossplane pulls the same content that had its signature verified. The fix has been applied to Crossplane's `main` branch and backported to the v2.3 and v2.2 release branches; it will be released in v2.3.3 and v2.2.3. ## Note on Fixed Versions The Crossplane maintainers are *not* planning to backport the fix for this advisory to the 1.20 branch, for two reasons: 1. The advisory is relevant only when an alpha feature is enabled and configured, and has a reasonable mitigation that is already a security best practice. 2. Doing so would require a major refactor of package manager internals to match the refactor that shipped in Crossplane v2.2. Such a refactor would be an unnecessary risk given the policy that v1.20 receives only critical fixes and that this advisory affects only users of an alpha feature. ## Credits This issue was reported, independently, by @bugbunny-research and @tonghuaroot.

Paquetes afectados y versiones corregidas

FuentePaqueteCorregido en
go::GitHub Security Advisory Gogithub.com/crossplane/crossplane, github.com/crossplane/crossplane/v22.3.3, 2.2.3
Mostrar las 2 entradas de 1 fuente
FuentePaqueteCorregido en
go::GitHub Security Advisory Gogithub.com/crossplane/crossplanesin corrección indicada
go::GitHub Security Advisory Gogithub.com/crossplane/crossplane/v22.3.3, 2.2.3

Referencias

Vulnerability data compiled from the Trivy vulnerability database (trivy-db, Aqua Security, Apache License 2.0), which aggregates third-party advisories. CVE records are published by The MITRE Corporation under the CVE Terms of Use; CVE is a trademark of MITRE. This product uses data from the NVD API but is not endorsed or certified by the NVD. Severity, titles and advisory data from the GitHub Advisory Database (CC BY 4.0), Red Hat security data (CC BY 4.0) and the other sources linked on each entry. Entries may be summarised or re-formatted; the linked original is the authoritative record.