{"answers":{"affected":"4 open source packages ship an affected version, including github.com/rancher/rancher. It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-22648 in the wild and no public exploit code.","fix":"Upgrade github.com/rancher/rancher to a fixed version for your release line: 2.6.13 or 2.7.4.","what":"CVE-2023-22648 is a high-severity vulnerability in SUSE Rancher, published on 1 Jun 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2023-22648 and fix it if it is affected.\n\nWhat it is: CVE-2023-22648 is a high-severity vulnerability in SUSE Rancher, published on 1 Jun 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2023-22648 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/rancher/rancher (Go): affected from 2.6.7; fixed in 2.6.13\n- github.com/rancher/rancher (Go): affected from 2.6.7; fixed in 2.6.13\n- github.com/rancher/rancher (Go): affected from 2.7.0; fixed in 2.7.4\n- github.com/rancher/rancher (Go): affected from 2.7.0; fixed in 2.7.4\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-22648/ (Markdown: https://insights.sbomify.com/CVE-2023-22648/index.md)","id":"CVE-2023-22648","markdown":"https://insights.sbomify.com/CVE-2023-22648/index.md","name":"CVE-2023-22648","record":{"aliases":["GHSA-vf6j-6739-78m8"],"analysis":{"component_type":"cloud_service","fix_type":"upgrade","impacts":["privilege_escalation","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Rancher management platform","requires_auth":"low_privilege","summary":"Users retain elevated Rancher permissions after Azure AD group changes, allowing unauthorized access to resources.","user_interaction":"required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"suse","cpe":[{"product":"rancher","vendor":"suse"}],"cvss":{"score":8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-271","name":"Privilege Dropping / Lowering Errors"}],"description":"A Improper Privilege Management vulnerability in SUSE Rancher causes permission changes in Azure AD not to be reflected to users \nwhile they are logged in the Rancher UI. This would cause the users to \nretain their previous permissions in Rancher, even if they change groups\n on Azure AD, for example, to a lower privileged group, or are removed \nfrom a group, thus retaining their access to Rancher instead of losing \nit.\nThis issue affects Rancher: from \u003e= 2.6.7 before \u003c 2.6.13, from \u003e= 2.7.0 before \u003c 2.7.4.","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Rancher's Azure AD permission changes are not reflected on active sessions","id":"CVE-2023-22648","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"privilege_escalation","year":"2023"},"n_packages":4,"n_references":2,"next":{"headline":"Rancher 'Audit Log' leaks sensitive information","id":"CVE-2023-22649"},"packages":[{"ecosystem":"Go","fixed":["2.6.13"],"introduced":["2.6.7"],"last_affected":[],"package":"github.com/rancher/rancher","purl":null,"source":"GHSA-vf6j-6739-78m8"},{"ecosystem":"Go","fixed":["2.6.13"],"introduced":["2.6.7"],"last_affected":[],"package":"github.com/rancher/rancher","purl":"pkg:golang/github.com/rancher/rancher","source":"GHSA-vf6j-6739-78m8"},{"ecosystem":"Go","fixed":["2.7.4"],"introduced":["2.7.0"],"last_affected":[],"package":"github.com/rancher/rancher","purl":null,"source":"GHSA-vf6j-6739-78m8"},{"ecosystem":"Go","fixed":["2.7.4"],"introduced":["2.7.0"],"last_affected":[],"package":"github.com/rancher/rancher","purl":"pkg:golang/github.com/rancher/rancher","source":"GHSA-vf6j-6739-78m8"}],"prev":{"headline":"Rancher vulnerable to Privilege Escalation via manipulation of Secrets","id":"CVE-2023-22647"},"products":["Rancher"],"published":"2023-06-01","related":[{"cvss_score":9.9,"headline":"Rancher vulnerable to Privilege Escalation via manipulation of Secrets","id":"CVE-2023-22647","kev_date_added":null,"published":"2023-06-01"},{"cvss_score":9.9,"headline":"Rancher Webhook is misconfigured during upgrade process","id":"CVE-2023-22651","kev_date_added":null,"published":"2023-05-04"},{"cvss_score":9.9,"headline":"Rancher: Exposure of sensitive fields","id":"CVE-2022-43757","kev_date_added":null,"published":"2023-02-07"},{"cvss_score":9.9,"headline":"Rancher: Plaintext storage and exposure of credentials in Rancher API and cluster.management.cattle.io object","id":"CVE-2021-36782","kev_date_added":null,"published":"2022-09-07"},{"cvss_score":9.9,"headline":"Rancher: Failure to properly sanitize credentials in cluster template answers","id":"CVE-2021-36783","kev_date_added":null,"published":"2022-09-07"},{"cvss_score":9.8,"headline":"Rancher Recreates Default User With Known Password Despite Deletion","id":"CVE-2019-11202","kev_date_added":null,"published":"2019-07-30"},{"cvss_score":9.5,"headline":"SAML Authentication Replay in Rancher","id":"CVE-2026-44946","kev_date_added":null,"published":"2026-06-30"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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-10-09","vendors":["SUSE"]},"summary":"Users retain elevated Rancher permissions after Azure AD group changes, allowing unauthorized access to resources.","url":"https://insights.sbomify.com/CVE-2023-22648/"}