CVE-2019-12274 json
Rancher Privilege Escalation Vulnerability
published 7y ago modified last mo. also GHSA-gc62-j469-9gjm , GO-2023-1991 , EUVD-2022-3935
- cvss
- 8.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.1%
- EPSS 1.1% chance of exploitation in 30 days, percentile 66%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- go github.com/rancher/rancher 1.6.27, 2.2.4, 2.2.4+incompatible
Is CVE-2019-12274 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
1.12% chance of exploitation in the next 30 days, higher than 66% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 8.8 | CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 4.0 | AV:N/AC:L/Au:S/C:P/I:N/A:N |
| GitHub | 3.0 | 8.8 | CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/rancher/rancher | >=2.0.0, <2.2.4 <1.6.27 >=2.0.0+incompatible, <2.2.4+incompatible |
2.2.4 1.6.27 2.2.4+incompatible |
Classification
References
-
forums.rancher.com
/c/announcements
release-notes, vendor-advisory
-
forums.rancher.com
/t/rancher-release-v2-2-4-addresses-rancher-cve-2019-12274-and-cve-2019-12303/14466
web, release-notes, vendor-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2019-12274
advisory
-
github.com
/advisories/GHSA-gc62-j469-9gjm
advisory
Sources
- CVE List CVE-2019-12274
- GitHub Advisory GHSA-gc62-j469-9gjm
- NVD CVE-2019-12274
- OSV GO-2023-1991
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.