ghsa-33hq-f2mf-jm3c
Vulnerability from github
Published
2023-05-25 16:58
Modified
2023-06-01 04:07
Severity ?
4.6 (Medium) - CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:L
Summary
kyverno seccomp control can be circumvented
Details

Impact

Users of the podSecurity (validate.podSecurity) subrule in Kyverno versions v1.9.2 and v1.9.3 may be unable to enforce the check for the Seccomp control at the baseline level when using a version value of latest. There is no effect if a version number is referenced instead. See the documentation for information on this subrule type. Users of Kyverno v1.9.2 and v1.9.3 are affected.

Patches

v1.9.4 v1.10.0

Workarounds

To work around this issue without upgrading to v1.9.4, temporarily install individual policies for the respective Seccomp checks in baseline here and restricted here.

References

  • https://kyverno.io/docs/writing-policies/validate/#pod-security
  • https://github.com/kyverno/kyverno/pull/7263
Show details on source website

To clipboard 

{
   affected: [
      {
         package: {
            ecosystem: "Go",
            name: "github.com/kyverno/kyverno",
         },
         ranges: [
            {
               events: [
                  {
                     introduced: "1.9.2",
                  },
                  {
                     fixed: "1.9.4",
                  },
               ],
               type: "ECOSYSTEM",
            },
         ],
      },
   ],
   aliases: [
      "CVE-2023-33191",
   ],
   database_specific: {
      cwe_ids: [
         "CWE-284",
      ],
      github_reviewed: true,
      github_reviewed_at: "2023-05-25T16:58:48Z",
      nvd_published_at: "2023-05-30T07:15:09Z",
      severity: "MODERATE",
   },
   details: "### Impact\n\nUsers of the podSecurity (`validate.podSecurity`) subrule in Kyverno versions v1.9.2 and v1.9.3 may be unable to enforce the check for the Seccomp control at the baseline level when using a `version` value of `latest`. There is no effect if a version number is referenced instead. See the [documentation](https://kyverno.io/docs/writing-policies/validate/#pod-security) for information on this subrule type. Users of Kyverno v1.9.2 and v1.9.3 are affected.\n\n### Patches\n\nv1.9.4\nv1.10.0\n\n### Workarounds\n\nTo work around this issue without upgrading to v1.9.4, temporarily install individual policies for the respective Seccomp checks in baseline [here](https://kyverno.io/policies/pod-security/baseline/restrict-seccomp/restrict-seccomp/) and restricted [here](https://kyverno.io/policies/pod-security/restricted/restrict-seccomp-strict/restrict-seccomp-strict/).\n\n### References\n\n* https://kyverno.io/docs/writing-policies/validate/#pod-security\n* https://github.com/kyverno/kyverno/pull/7263\n",
   id: "GHSA-33hq-f2mf-jm3c",
   modified: "2023-06-01T04:07:20Z",
   published: "2023-05-25T16:58:48Z",
   references: [
      {
         type: "WEB",
         url: "https://github.com/kyverno/kyverno/security/advisories/GHSA-33hq-f2mf-jm3c",
      },
      {
         type: "ADVISORY",
         url: "https://nvd.nist.gov/vuln/detail/CVE-2023-33191",
      },
      {
         type: "WEB",
         url: "https://github.com/kyverno/kyverno/pull/7263",
      },
      {
         type: "PACKAGE",
         url: "https://github.com/kyverno/kyverno",
      },
      {
         type: "WEB",
         url: "https://github.com/kyverno/kyverno/releases/tag/v1.9.4",
      },
   ],
   schema_version: "1.4.0",
   severity: [
      {
         score: "CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:L",
         type: "CVSS_V3",
      },
   ],
   summary: "kyverno seccomp control can be circumvented",
}


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.