Описание
A build step for a Git source, crafted in a specific way, can bypass some policy validation rules. A malicious build definition can make the repository look like it is coming from a different remote URL than it really is when Git clone is happening. If policy is doing more stricter validation, for example based on commit SHA, commit data, or signatures, then all these validations still apply correctly.
A flaw was found in BuildKit. An attacker with the ability to define build steps can bypass policy validation rules by supplying a specially crafted Git source. During a clone operation, this issue allows the repository to spoof its remote URL, making untrusted source code appear to originate from an authorized repository. Consequently, builds relying strictly on repository URL validation may ingest unauthorized code, compromising build pipeline integrity.
Отчет
A flaw was found in BuildKit's Git source resolution logic when evaluating remote repository URLs. An authenticated user capable of defining build steps can craft a Git source definition that spoofs its remote URL during clone operations, bypassing source-repository policy filters. Build pipelines that enforce access control or provenance solely by repository URL may ingest untrusted source code, leading to build artifact tampering and unauthorized code execution within the build container. Stricter validation mechanisms using commit SHAs or cryptographic commit signatures remain unaffected.
Меры по смягчению последствий
Configure build pipelines and admission policies to validate Git sources using immutable commit SHAs or cryptographic commit signatures rather than repository URLs alone. Restrict build definition privileges in CI/CD pipelines to trusted contributors.
Затронутые пакеты
| Платформа | Пакет | Состояние | Рекомендация | Релиз |
|---|---|---|---|---|
| Red Hat Hardened Images | buildah | Not affected | ||
| Red Hat Hardened Images | podman | Not affected | ||
| Red Hat Hardened Images | trivy | Not affected | ||
| Red Hat Quay 3 | quay/quay-builder-rhel8 | Fix deferred | ||
| Red Hat Quay 3 | quay/quay-builder-rhel9 | Fix deferred |
Показывать по
Дополнительная информация
Статус:
EPSS
5.9 Medium
CVSS3
Связанные уязвимости
A build step for a Git source, crafted in a specific way, can bypass some policy validation rules. A malicious build definition can make the repository look like it is coming from a different remote URL than it really is when Git clone is happening. If policy is doing more stricter validation, for example based on commit SHA, commit data, or signatures, then all these validations still apply correctly.
A build step for a Git source, crafted in a specific way, can bypass some policy validation rules. A malicious build definition can make the repository look like it is coming from a different remote URL than it really is when Git clone is happening. If policy is doing more stricter validation, for example based on commit SHA, commit data, or signatures, then all these validations still apply correctly.
A build step for a Git source, crafted in a specific way, can bypass s ...
EPSS
5.9 Medium
CVSS3