{"answers":{"affected":"5 open source packages ship an affected version, including github.com/rancher/rancher. It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-12274 in the wild and no public exploit code.","fix":"Upgrade github.com/rancher/rancher to a fixed version for your release line: 1.6.27, 2.2.4+incompatible or 2.2.4.","what":"CVE-2019-12274 is a high-severity vulnerability in n/a, published on 6 Jun 2019. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-12274 and fix it if it is affected.\n\nWhat it is: CVE-2019-12274 is a high-severity vulnerability in n/a, published on 6 Jun 2019. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-12274 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/rancher/rancher (Go): affected all versions; fixed in 1.6.27, 2.2.4+incompatible\n- github.com/rancher/rancher (Go): affected all versions; fixed in 1.6.27\n- github.com/rancher/rancher (Go): affected all versions; fixed in 1.6.27\n- github.com/rancher/rancher (Go): affected from 2.0.0; fixed in 2.2.4\n- github.com/rancher/rancher (Go): affected from 2.0.0; fixed in 2.2.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-2019-12274/ (Markdown: https://insights.sbomify.com/CVE-2019-12274/index.md)","id":"CVE-2019-12274","markdown":"https://insights.sbomify.com/CVE-2019-12274/index.md","name":"CVE-2019-12274","record":{"aliases":["GHSA-gc62-j469-9gjm","GO-2023-1991"],"analysis":{"component_type":"cloud_service","fix_type":"patch","impacts":["privilege_escalation","data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Rancher management plane","requires_auth":"low_privilege","summary":"Unprivileged users with node deployment rights can escalate to admin by exfiltrating sensitive kubeconfig files via node driver options.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"rancher","vendor":"suse"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"},{"id":"CWE-668","name":"Exposure of Resource to Wrong Sphere"}],"description":"In Rancher 1 and 2 through 2.2.3, unprivileged users (if allowed to deploy nodes) can gain admin access to the Rancher management plane because node driver options intentionally allow posting certain data to the cloud. The problem is that a user could choose to post a sensitive file such as /root/.kube/config or /var/lib/rancher/management-state/cred/kubeconfig-system.yaml.","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 Privilege Escalation Vulnerability","id":"CVE-2019-12274","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"privilege_escalation","year":"2019"},"n_packages":5,"n_references":2,"next":{"headline":"Path traversal in n/a","id":"CVE-2019-12276"},"packages":[{"ecosystem":"Go","fixed":["1.6.27","2.2.4+incompatible"],"introduced":["0","2.0.0+incompatible"],"last_affected":[],"package":"github.com/rancher/rancher","purl":"pkg:golang/github.com/rancher/rancher","source":"GO-2023-1991"},{"ecosystem":"Go","fixed":["1.6.27"],"introduced":["0"],"last_affected":[],"package":"github.com/rancher/rancher","purl":null,"source":"GHSA-gc62-j469-9gjm"},{"ecosystem":"Go","fixed":["1.6.27"],"introduced":["0"],"last_affected":[],"package":"github.com/rancher/rancher","purl":"pkg:golang/github.com/rancher/rancher","source":"GHSA-gc62-j469-9gjm"},{"ecosystem":"Go","fixed":["2.2.4"],"introduced":["2.0.0"],"last_affected":[],"package":"github.com/rancher/rancher","purl":null,"source":"GHSA-gc62-j469-9gjm"},{"ecosystem":"Go","fixed":["2.2.4"],"introduced":["2.0.0"],"last_affected":[],"package":"github.com/rancher/rancher","purl":"pkg:golang/github.com/rancher/rancher","source":"GHSA-gc62-j469-9gjm"}],"prev":{"headline":"Cross-site request forgery in n/a","id":"CVE-2019-12273"},"products":["n/a"],"published":"2019-06-06","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":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"},{"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":"Unprivileged users with node deployment rights can escalate to admin by exfiltrating sensitive kubeconfig files via node driver options.","url":"https://insights.sbomify.com/CVE-2019-12274/"}