tyra Open Policy Agent (OPA) Gatekeeper through 3.7.0 mishandles concurrency, sometimes resulting in incorrect access control. The data replication mechanism allows policies to access the Kubernetes cluster state. During data replication, OPA/Gatekeeper does not wait for the replication to finish before processing a request, which might cause inconsistencies between the replicated resources in OPA/Gatekeeper and the resources actually present in the cluster. Inconsistency can later be reflected in a policy bypass. NOTE: the vendor disagrees that this is a vulnerability, because Kubernetes states are only eventually consistent
| Link | Resource |
|---|---|
| https://github.com/hkerma/opa-gatekeeper-concurrency-issue | Third Party Advisory |
| https://github.com/open-policy-agent/gatekeeper/releases | Patch Third Party Advisory |
| https://github.com/hkerma/opa-gatekeeper-concurrency-issue | Third Party Advisory |
| https://github.com/open-policy-agent/gatekeeper/releases | Patch Third Party Advisory |
21 Nov 2024, 06:30
| Type | Values Removed | Values Added |
|---|---|---|
| References | () https://github.com/hkerma/opa-gatekeeper-concurrency-issue - Third Party Advisory | |
| References | () https://github.com/open-policy-agent/gatekeeper/releases - Patch, Third Party Advisory |
Published : 2021-11-17 19:15
Updated : 2024-11-21 06:30
NVD link : CVE-2021-43979
Mitre link : CVE-2021-43979
CVE.ORG link : CVE-2021-43979
JSON object : View
Always-Incorrect Control Flow Implementation