Описание
Renovate is a dependency update automation tool. In versions before 44.3.1 (and Mend Renovate CE/EE images before 15.4.0, mend-renovate-ce Helm chart before 15.4.0, mend-renovate-enterprise-edition Helm chart before 10.4.0), digest updates are not subject to the internal minimumReleaseAge (stability age) checks. When a repository configures minimumReleaseAge and has dependencies with updateType=digest — for example GitHub Actions pinned to a commit SHA with a floating tag, Docker images, Go modules or NuGet packages — Renovate will still open a pull request for a newly published digest, marked only with a pending renovate/stability-days status check. A newly published, potentially malicious dependency version can therefore cause a PR to be raised and CI workflows to potentially run before the configured minimum release age has elapsed, which is precisely what the Minimum Release Age control is intended to prevent. The issue is fixed in Renovate 44.3.1; as a workaround, digest updates can be disabled or gated behind dependencyDashboardApproval.
A flaw was found in Renovate, a dependency update automation tool. This vulnerability allows for the bypass of the minimumReleaseAge security control when processing digest updates. A remote attacker could exploit this by publishing a malicious dependency version, which Renovate would then prematurely propose in a pull request, potentially leading to the execution of untrusted code in continuous integration (CI) workflows before stability checks are complete. This undermines the intended protection against unstable or malicious dependency introductions.
Отчет
This Moderate impact flaw in Renovate, as used in Red Hat Konflux's mintmaker-renovate-image, allows digest updates to bypass configured minimumReleaseAge checks. This circumvents a critical security control, potentially leading to automated pull requests and CI workflow execution for newly published, unvetted, or malicious dependency versions before their stability age has elapsed. The impact is limited to environments where minimumReleaseAge is configured and digest updates are in use.
Меры по смягчению последствий
To mitigate this issue, disable digest updates or gate them behind dependencyDashboardApproval in your Renovate configuration. This prevents the automatic processing of new digests before the minimumReleaseAge checks are applied.
Дополнительная информация
Статус:
EPSS
5.8 Medium
CVSS3
Связанные уязвимости
Renovate is a dependency update automation tool. In versions before 44.3.1 (and Mend Renovate CE/EE images before 15.4.0, mend-renovate-ce Helm chart before 15.4.0, mend-renovate-enterprise-edition Helm chart before 10.4.0), digest updates are not subject to the internal `minimumReleaseAge` (stability age) checks. When a repository configures `minimumReleaseAge` and has dependencies with `updateType=digest` — for example GitHub Actions pinned to a commit SHA with a floating tag, Docker images, Go modules or NuGet packages — Renovate will still open a pull request for a newly published digest, marked only with a pending `renovate/stability-days` status check. A newly published, potentially malicious dependency version can therefore cause a PR to be raised and CI workflows to potentially run before the configured minimum release age has elapsed, which is precisely what the Minimum Release Age control is intended to prevent. The issue is fixed in Renovate 44.3.1; as a workaround, dige
Renovate is a dependency update automation tool. In versions before 44.3.1 (and Mend Renovate CE/EE images before 15.4.0, mend-renovate-ce Helm chart before 15.4.0, mend-renovate-enterprise-edition Helm chart before 10.4.0), digest updates are not subject to the internal `minimumReleaseAge` (stability age) checks. When a repository configures `minimumReleaseAge` and has dependencies with `updateType=digest` — for example GitHub Actions pinned to a commit SHA with a floating tag, Docker images, Go modules or NuGet packages — Renovate will still open a pull request for a newly published digest, marked only with a pending `renovate/stability-days` status check. A newly published, potentially malicious dependency version can therefore cause a PR to be raised and CI workflows to potentially run before the configured minimum release age has elapsed, which is precisely what the Minimum Release Age control is intended to prevent. The issue is fixed in Renovate 44.3.1; as a workaround, d...
EPSS
5.8 Medium
CVSS3