Skip to content

kyverno seccomp control can be circumvented

Moderate severity GitHub Reviewed Published May 25, 2023 in kyverno/kyverno • Updated Nov 5, 2023

Package

gomod github.com/kyverno/kyverno (Go)

Affected versions

>= 1.9.2, < 1.9.4

Patched versions

1.9.4

Description

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

References

@chipzoller chipzoller published to kyverno/kyverno May 25, 2023
Published to the GitHub Advisory Database May 25, 2023
Reviewed May 25, 2023
Published by the National Vulnerability Database May 30, 2023
Last updated Nov 5, 2023

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
Low
User interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:L

EPSS score

0.223%
(61st percentile)

Weaknesses

CVE ID

CVE-2023-33191

GHSA ID

GHSA-33hq-f2mf-jm3c

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.