diff --git a/advisories/github-reviewed/2022/12/GHSA-m3cq-xcx9-3gvm/GHSA-m3cq-xcx9-3gvm.json b/advisories/github-reviewed/2022/12/GHSA-m3cq-xcx9-3gvm/GHSA-m3cq-xcx9-3gvm.json
index cdfda34ebaa..34f1ba0dad9 100644
--- a/advisories/github-reviewed/2022/12/GHSA-m3cq-xcx9-3gvm/GHSA-m3cq-xcx9-3gvm.json
+++ b/advisories/github-reviewed/2022/12/GHSA-m3cq-xcx9-3gvm/GHSA-m3cq-xcx9-3gvm.json
@@ -1,10 +1,10 @@
 {
   "schema_version": "1.3.0",
   "id": "GHSA-m3cq-xcx9-3gvm",
-  "modified": "2022-12-21T17:24:10Z",
+  "modified": "2022-12-22T16:40:54Z",
   "published": "2022-12-21T17:24:10Z",
   "aliases": [
-
+    "CVE-2022-47633"
   ],
   "summary": "Bypass of verifyImages rule 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",