{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2021-20238 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-20238 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-20238 is a low-severity missing authorization vulnerability in Redhat Openshift Container Platform, published on 1 Apr 2022. 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-20238 and fix it if it is affected.\n\nWhat it is: CVE-2021-20238 is a low-severity missing authorization vulnerability in Redhat Openshift Container Platform, published on 1 Apr 2022. 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-20238 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-20238/ (Markdown: https://insights.sbomify.com/CVE-2021-20238/index.md)","id":"CVE-2021-20238","markdown":"https://insights.sbomify.com/CVE-2021-20238/index.md","name":"CVE-2021-20238","record":{"aliases":[],"analysis":{"component_type":"container_or_infrastructure","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"OpenShift Container Platform","requires_auth":"none","summary":"Attackers can access sensitive ignition configuration data, including registry secrets, from the Machine Config Server without authentication in specific deployment scenarios.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"openshift_container_platform","vendor":"redhat"},{"product":"openshift_machine-config-operator","vendor":"redhat"}],"cvss":{"score":3.7,"severity":"low","source":"nvd","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-306","name":"Missing Authentication for Critical Functionality"},{"id":"CWE-287","name":"Improper Authentication"}],"description":"It was found in OpenShift Container Platform 4 that ignition config, served by the Machine Config Server, can be accessed externally from clusters without authentication. The MCS endpoint (port 22623) provides ignition configuration used for bootstrapping Nodes and can include some sensitive data, e.g. registry pull secrets. There are two scenarios where this data can be accessed. The first is on Baremetal, OpenStack, Ovirt, Vsphere and KubeVirt deployments which do not have a separate internal API endpoint and allow access from outside the cluster to port 22623 from the standard OpenShift API Virtual IP address. The second is on cloud deployments when using unsupported network plugins, which do not create iptables rules that prevent to port 22623. In this scenario, the ignition config is exposed to all pods within the cluster and cannot be accessed externally.","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":"Missing authorization in openshift/machine-config-operator","id":"CVE-2021-20238","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"redhat:openshift_container_platform","products":["redhat:openshift_container_platform"],"type":"missing_authorization","year":"2021"},"n_packages":0,"n_references":1,"next":{"headline":"Information disclosure in kernel","id":"CVE-2021-20239"},"packages":[],"prev":{"headline":"Denial of service in zeromq","id":"CVE-2021-20237"},"products":["openshift/machine-config-operator"],"published":"2022-04-01","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":"Privilege escalation in openshift","id":"CVE-2021-20182","kev_date_added":null,"published":"2021-02-23"},{"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 can access sensitive ignition configuration data, including registry secrets, from the Machine Config Server without authentication in specific deployment scenarios.","url":"https://insights.sbomify.com/CVE-2021-20238/"}