Miggo Logo

CVE-2024-48921: Kyverno's PolicyException objects can be created in any namespace by default

7.5

CVSS Score
3.1

Basic Information

EPSS Score
0.05748%
Published
10/29/2024
Updated
11/7/2024
KEV Status
No
Technology
TechnologyGo

Technical Details

CVSS Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Package NameEcosystemVulnerable VersionsFirst Patched Version
github.com/kyverno/kyvernogo< 1.13.01.13.0

Vulnerability Intelligence
Miggo AIMiggo AI

Miggo AIRoot Cause Analysis

The vulnerability arises because Kyverno's PolicyException handling did not restrict exceptions to specific namespaces. Functions responsible for processing or validating PolicyExceptions (e.g., reconciliation logic and policy exception checks) would need to enforce namespace constraints to prevent unauthorized overrides. The confidence is medium because the exact code flow isn't visible, but the described vulnerability mechanics strongly implicate these components. The patched version (1.13.0) likely introduced namespace-scoping logic in these areas.

Vulnerable functions

Only Mi**o us*rs **n s** t*is s**tion

WAF Protection Rules

WAF Rule

### Summ*ry * kyv*rno *lust*rPoli*y, i*. "*is*llow-privil****-*ont*in*rs," **n ** ov*rri***n *y t** *r**tion o* * Poli*y*x**ption in * r*n*om n*m*sp***. ### **t*ils *y **si*n, Poli*y*x**ptions *r* *onsum** *rom *ny n*m*sp***. **ministr*tors m*y not

Reasoning

T** vuln*r**ility *ris*s ****us* Kyv*rno's Poli*y*x**ption **n*lin* *i* not r*stri*t *x**ptions to sp**i*i* n*m*sp***s. *un*tions r*sponsi*l* *or pro**ssin* or v*li**tin* Poli*y*x**ptions (*.*., r**on*ili*tion lo*i* *n* poli*y *x**ption ****ks) woul*