mirror of
https://github.com/netbirdio/advisory-database.git
synced 2026-05-22 18:04:22 -07:00
Publish GHSA-m3cq-xcx9-3gvm
This commit is contained in:
@@ -1,13 +1,13 @@
|
||||
{
|
||||
"schema_version": "1.4.0",
|
||||
"id": "GHSA-m3cq-xcx9-3gvm",
|
||||
"modified": "2023-08-29T22:40:39Z",
|
||||
"modified": "2025-04-15T12:50:46Z",
|
||||
"published": "2022-12-21T17:24:10Z",
|
||||
"aliases": [
|
||||
"CVE-2022-47633"
|
||||
],
|
||||
"summary": "kyverno verifyImages rule bypass possible with malicious proxy/registry",
|
||||
"details": "### Impact\n\nUsers of Kyverno on versions 1.8.3 or 1.8.4 who use `verifyImages` rules to verify container image signatures, and do not prevent use of unknown registries.\n\n### Patches\n\nThis issue has been fixed in version [1.8.5](https://github.com/kyverno/kyverno/releases/tag/v1.8.5)\n\n### Workarounds\n\nConfigure a Kyverno policy to restrict registries to a set of secure trusted image registries ([sample](https://kyverno.io/policies/best-practices/restrict_image_registries/restrict_image_registries/)).\n\n### References\n\n\n",
|
||||
"details": "### Impact\n\nUsers of Kyverno on versions 1.8.3 or 1.8.4 who use `verifyImages` rules to verify container image signatures, and do not prevent use of unknown registries.\n\n### Patches\n\nThis issue has been fixed in version [1.8.5](https://github.com/kyverno/kyverno/releases/tag/v1.8.5)\n\n### Workarounds\n\nConfigure a Kyverno policy to restrict registries to a set of secure trusted image registries ([sample](https://kyverno.io/policies/best-practices/restrict_image_registries/restrict_image_registries/)).\n\n### References",
|
||||
"severity": [
|
||||
{
|
||||
"type": "CVSS_V3",
|
||||
|
||||
Reference in New Issue
Block a user