{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-20182 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-20182 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-20182 is a high-severity vulnerability in Redhat Openshift Container Platform, published on 23 Feb 2021. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-20182 and fix it if it is affected.\n\nWhat it is: CVE-2021-20182 is a high-severity vulnerability in Redhat Openshift Container Platform, published on 23 Feb 2021. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2021-20182 in the wild and no public exploit code.\n\nAffected product: Redhat Openshift Container Platform. 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-20182/ (Markdown: https://insights.sbomify.com/CVE-2021-20182/index.md)","id":"CVE-2021-20182","markdown":"https://insights.sbomify.com/CVE-2021-20182/index.md","name":"CVE-2021-20182","record":{"aliases":[],"analysis":{"component_type":"container_or_infrastructure","fix_type":"patch","impacts":["privilege_escalation","data_read","data_modify","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"OpenShift build container","requires_auth":"low_privilege","summary":"Attackers with build container access can escalate privileges to cluster admin by exploiting raw device access in the chrooted environment.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"openshift_container_platform","vendor":"redhat"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-552","name":"Files or Directories Accessible to External Parties"}],"description":"A privilege escalation flaw was found in openshift4/ose-docker-builder. The build container runs with high privileges using a chrooted environment instead of runc. If an attacker can gain access to this build container, they can potentially utilize the raw devices of the underlying node, such as the network and storage devices, to at least escalate their privileges to that of the cluster admin. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Privilege escalation in openshift","id":"CVE-2021-20182","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"redhat:openshift_container_platform","products":["redhat:openshift_container_platform"],"type":"privilege_escalation","year":"2021"},"n_packages":0,"n_references":1,"next":{"headline":"Moodle Vulnerable to Reflected Cross-site Scripting","id":"CVE-2021-20183"},"packages":[],"prev":{"headline":"Use after free in qemu","id":"CVE-2021-20181"},"products":["openshift"],"published":"2021-02-23","related":[{"cvss_score":9.8,"headline":"Missing authorization in cluster-ingress-operator","id":"CVE-2020-27836","kev_date_added":null,"published":"2022-08-22"},{"cvss_score":9,"headline":"Misconfiguration in openshift-ansible","id":"CVE-2018-1085","kev_date_added":null,"published":"2018-06-15"},{"cvss_score":8.8,"headline":"Privilege escalation in Red Hat OpenShift Container Platform 4","id":"CVE-2026-54099","kev_date_added":null,"published":"2026-06-22"},{"cvss_score":8.8,"headline":"Ose-cluster-ingress-operator: remote code execution through haproxy configuration injection","id":"CVE-2026-1784","kev_date_added":null,"published":"2026-06-02"},{"cvss_score":8.8,"headline":"xterm vulnerable to remote code execution","id":"CVE-2019-0542","kev_date_added":null,"published":"2019-01-09"},{"cvss_score":8.5,"headline":"Privilege escalation in source-to-image","id":"CVE-2018-10843","kev_date_added":null,"published":"2018-07-02"}],"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-03","vendors":["n/a"]},"summary":"Attackers with build container access can escalate privileges to cluster admin by exploiting raw device access in the chrooted environment.","url":"https://insights.sbomify.com/CVE-2021-20182/"}