{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-3027 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-3027 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-3027 is a high-severity vulnerability in RHACM, published on 5 Jun 2023. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-3027 and fix it if it is affected.\n\nWhat it is: CVE-2023-3027 is a high-severity vulnerability in RHACM, published on 5 Jun 2023. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-3027 in the wild and no public exploit code.\n\nAffected product: RHACM. 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-2023-3027/ (Markdown: https://insights.sbomify.com/CVE-2023-3027/index.md)","id":"CVE-2023-3027","markdown":"https://insights.sbomify.com/CVE-2023-3027/index.md","name":"CVE-2023-3027","record":{"aliases":["GHSA-ffmc-4rrr-xm85"],"analysis":{"component_type":"cloud_service","fix_type":"patch","impacts":["privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Red Hat Advanced Cluster Management","requires_auth":"low_privilege","summary":"Attackers can escalate privileges within the cluster by exploiting improper namespace restrictions in dynamically obtained policy values.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"advanced_cluster_management_for_kubernetes","vendor":"redhat"}],"cvss":{"score":7.8,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"},{"id":"CWE-269","name":"Improper Privilege Management"}],"description":"The grc-policy-propagator allows security escalation within the cluster. The propagator allows policies which contain some dynamically obtained values (instead of the policy apply a static manifest on a managed cluster) of taking advantage of cluster scoped access in a created policy. This feature does not restrict properly to lookup content from the namespace where the policy was created.","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 RHACM","id":"CVE-2023-3027","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"Improper backend communication allows access and manipulation of the telemetry data","id":"CVE-2023-3028"},"packages":[],"prev":{"headline":"Cross-site Scripting (XSS) - Stored in jgraph/drawio","id":"CVE-2023-3026"},"products":["RHACM"],"published":"2023-06-05","related":[{"cvss_score":8.2,"headline":"Open Cluster Management (OCM): Cross-cluster privilege escalation via improper Kubernetes client certificate renewal validation","id":"CVE-2026-4740","kev_date_added":null,"published":"2026-04-07"},{"cvss_score":7.8,"headline":"Server-side request forgery in RHACM","id":"CVE-2022-3841","kev_date_added":null,"published":"2023-01-11"},{"cvss_score":7.1,"headline":"Insights-client-rhel9: insights-client: pull-secret bearer token written to logs on non-200 ccx response","id":"CVE-2026-71474","kev_date_added":null,"published":"2026-08-11"},{"cvss_score":6.8,"headline":"Insights-client-rhel9: insights-client: spoke-controlled clusterid injected unencoded into insights api url path","id":"CVE-2026-71475","kev_date_added":null,"published":"2026-08-11"},{"cvss_score":6.5,"headline":"Insights-client: insights-client: clusterrole grants cluster-wide secrets get/list/watch beyond least privilege","id":"CVE-2026-71846","kev_date_added":null,"published":"2026-08-12"},{"cvss_score":6.5,"headline":"SQL injection in Red Hat Advanced Cluster Management for Kubernetes","id":"CVE-2022-2238","kev_date_added":null,"published":"2022-09-01"}],"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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-01-08","vendors":["n/a"]},"summary":"Attackers can escalate privileges within the cluster by exploiting improper namespace restrictions in dynamically obtained policy values.","url":"https://insights.sbomify.com/CVE-2023-3027/"}