-
Notifications
You must be signed in to change notification settings - Fork 136
[cloud-provider-yandex] fixed CVE #16611
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Signed-off-by: Artem Darmanyan <artem.darmanyan@flant.com>
|
🟢 Workflow detailsYandex.Cloud-WithoutNAT-Containerd-1.32 - Connection string: 🟢 |
|
🔴 Workflow details (1 job failed)🔴 |
Signed-off-by: Artem Darmanyan <artem.darmanyan@flant.com>
|
🟢 Workflow detailsYandex.Cloud-WithoutNAT-Containerd-1.32 - Connection string: 🟢 |
|
🟢 Workflow details🟢 |
|
🟢 Workflow detailsYandex.Cloud-WithoutNAT-Containerd-1.32 - Connection string: 🟢 |
|
🟢 Workflow details🟢 |
Signed-off-by: Artem Darmanyan <artem.darmanyan@flant.com>
Signed-off-by: Artem Darmanyan <artem.darmanyan@flant.com>
|
🟢 Workflow detailsYandex.Cloud-WithoutNAT-Containerd-1.32 - Connection string: 🟢 |
Signed-off-by: Artem Darmanyan <artem.darmanyan@flant.com>
Signed-off-by: Artem Darmanyan <artem.darmanyan@flant.com>
|
🟢 Workflow detailsYandex.Cloud-WithoutNAT-Containerd-1.32 - Connection string: 🟢 |
|
🟢 Workflow details🟢 |
--------- Signed-off-by: Artem Darmanyan <artem.darmanyan@flant.com> Co-authored-by: Artem Darmanyan <artem.darmanyan@flant.com>
|
Cherry pick PR 16769 to the branch release-1.73 successful! |
|
/backport 1.74 |
--------- Signed-off-by: Artem Darmanyan <artem.darmanyan@flant.com> Co-authored-by: Artem Darmanyan <artem.darmanyan@flant.com>
|
Cherry pick PR 16783 to the branch release-1.74 successful! |
Description
Fixed CVE
This PR updates dependencies used in all Yandex cloud-provider components to fix previously identified CVEs.
After updating the modules and rebuilding the images, all cloudProviderYandex artifacts (cloud-controller-manager, cloud-data-discoverer, cloud-migrator, metrics-exporter, and yandex-csi-plugin) were rescanned with Trivy.
According to the latest scan results:
All CVEs that were previously detected in Yandex components have been fully resolved.
All five Yandex module reports now contain no vulnerabilities at all, confirming that the dependency updates were applied correctly.
Why do we need it, and what problem does it solve?
Removes HIGH-severity CVEs detected by Trivy in the cloudProviderYandex module.
Ensures the Yandex provider remains compliant with Deckhouse’s security baseline.
Aligns the module with patched versions of Go libraries (jwt, x/net, x/oauth2, x/crypto).
Eliminates false-positives in CI and restores a clean security state for all Yandex images.
Why do we need it in the patch release (if we do)?
Checklist
Changelog entries