{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-43979 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-43979 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-43979 is a medium-severity vulnerability in n/a, published on 17 Nov 2021. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-43979 and fix it if it is affected.\n\nWhat it is: CVE-2021-43979 is a medium-severity vulnerability in n/a, published on 17 Nov 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2021-43979 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2021-43979/ (Markdown: https://insights.sbomify.com/CVE-2021-43979/index.md)","id":"CVE-2021-43979","markdown":"https://insights.sbomify.com/CVE-2021-43979/index.md","name":"CVE-2021-43979","record":{"aliases":["GHSA-v8hv-78vf-x9fr"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"no_fix_stated","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Kubernetes policy engine","requires_auth":"none","summary":"Attackers can bypass access control policies in OPA Gatekeeper due to a race condition during data replication, allowing unauthorized actions.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"gatekeeper","vendor":"openpolicyagent"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-670","name":"Always-Incorrect Control Flow Implementation"}],"description":"Styra 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","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Race condition in n/a","id":"CVE-2021-43979","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2021"},"n_packages":0,"n_references":2,"next":{"headline":"Apache Tomcat: Information disclosure","id":"CVE-2021-43980"},"packages":[],"prev":{"headline":"Hardcoded credentials in n/a","id":"CVE-2021-43978"},"products":["n/a"],"published":"2021-11-17","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Attackers can bypass access control policies in OPA Gatekeeper due to a race condition during data replication, allowing unauthorized actions.","url":"https://insights.sbomify.com/CVE-2021-43979/"}