ghsa-m3cq-xcx9-3gvm
Vulnerability from github
Published
2022-12-21 17:24
Modified
2023-08-29 22:40
Severity ?
8.1 (High) - CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Summary
kyverno verifyImages rule bypass possible with malicious proxy/registry
Details

Impact

Users 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.

Patches

This issue has been fixed in version 1.8.5

Workarounds

Configure a Kyverno policy to restrict registries to a set of secure trusted image registries (sample).

References

Show details on source website

To clipboard 

{
   affected: [
      {
         package: {
            ecosystem: "Go",
            name: "github.com/kyverno/kyverno",
         },
         ranges: [
            {
               events: [
                  {
                     introduced: "1.8.3",
                  },
                  {
                     fixed: "1.8.5",
                  },
               ],
               type: "ECOSYSTEM",
            },
         ],
      },
   ],
   aliases: [
      "CVE-2022-47633",
   ],
   database_specific: {
      cwe_ids: [
         "CWE-287",
      ],
      github_reviewed: true,
      github_reviewed_at: "2022-12-21T17:24:10Z",
      nvd_published_at: "2022-12-23T23:15:00Z",
      severity: "HIGH",
   },
   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",
   id: "GHSA-m3cq-xcx9-3gvm",
   modified: "2023-08-29T22:40:39Z",
   published: "2022-12-21T17:24:10Z",
   references: [
      {
         type: "WEB",
         url: "https://github.com/kyverno/kyverno/security/advisories/GHSA-m3cq-xcx9-3gvm",
      },
      {
         type: "ADVISORY",
         url: "https://nvd.nist.gov/vuln/detail/CVE-2022-47633",
      },
      {
         type: "WEB",
         url: "https://github.com/kyverno/kyverno/pull/5713",
      },
      {
         type: "PACKAGE",
         url: "https://github.com/kyverno/kyverno",
      },
      {
         type: "WEB",
         url: "https://github.com/kyverno/kyverno/compare/v1.8.4...v1.8.5",
      },
      {
         type: "WEB",
         url: "https://github.com/kyverno/kyverno/releases/tag/v1.8.5",
      },
      {
         type: "WEB",
         url: "https://kyverno.io/docs/writing-policies/verify-images",
      },
      {
         type: "WEB",
         url: "https://kyverno.io/policies/best-practices/restrict_image_registries/restrict_image_registries",
      },
      {
         type: "WEB",
         url: "https://pkg.go.dev/vuln/GO-2022-1180",
      },
      {
         type: "WEB",
         url: "https://web.archive.org/web/20230426095744/https://kyverno.io/policies/best-practices/restrict_image_registries/restrict_image_registries",
      },
   ],
   schema_version: "1.4.0",
   severity: [
      {
         score: "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H",
         type: "CVSS_V3",
      },
   ],
   summary: "kyverno verifyImages rule bypass possible with malicious proxy/registry",
}


Log in or create an account to share your comment.

Security Advisory comment format.

This schema specifies the format of a comment related to a security advisory.

UUIDv4 of the comment
UUIDv4 of the Vulnerability-Lookup instance
When the comment was created originally
When the comment was last updated
Title of the comment
Description of the comment
The identifier of the vulnerability (CVE ID, GHSA-ID, PYSEC ID, etc.).



Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.