{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-10200 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-10200 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-10200 is a high-severity vulnerability in Redhat Openshift Container Platform, published on 19 Mar 2021. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-10200 and fix it if it is affected.\n\nWhat it is: CVE-2019-10200 is a high-severity vulnerability in Redhat Openshift Container Platform, published on 19 Mar 2021. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-10200 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-2019-10200/ (Markdown: https://insights.sbomify.com/CVE-2019-10200/index.md)","id":"CVE-2019-10200","markdown":"https://insights.sbomify.com/CVE-2019-10200/index.md","name":"CVE-2019-10200","record":{"aliases":["GHSA-8283-mprv-vc6w"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"patch","impacts":["privilege_escalation","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"OpenShift Container Platform","requires_auth":"high_privilege","summary":"Users with pod creation rights can schedule pods on master nodes to steal AWS IAM credentials, gaining full infrastructure control.","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":7.2,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-284","name":"Improper Access Control"}],"description":"A flaw was discovered in OpenShift Container Platform 4 where, by default, users with access to create pods also have the ability to schedule workloads on master nodes. Pods with permission to access the host network, running on master nodes, can retrieve security credentials for the master AWS IAM role, allowing management access to AWS resources. With access to the security credentials, the user then has access to the entire infrastructure. Impact to data and system availability is high.","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 Container Platform","id":"CVE-2019-10200","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"redhat:openshift_container_platform","products":["redhat:openshift_container_platform"],"type":"privilege_escalation","year":"2019"},"n_packages":0,"n_references":2,"next":{"headline":"Improper Verification of Cryptographic Signature in keycloak","id":"CVE-2019-10201"},"packages":[],"prev":{"headline":"Improper Input Validation and Cross-Site Request Forgery in Keycloak","id":"CVE-2019-10199"},"products":["OpenShift Container Platform"],"published":"2021-03-19","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-04","vendors":["n/a"]},"summary":"Users with pod creation rights can schedule pods on master nodes to steal AWS IAM credentials, gaining full infrastructure control.","url":"https://insights.sbomify.com/CVE-2019-10200/"}