CVE-2019-10150 json
It was found that OpenShift Container Platform versions 3.6.x - 4.6.0 does not perform SSH Host Key checking when using ssh key authenticat…
published 2019-06-12 7 y ago modified 2026-06-17 4 mo ago also EUVD-2019-2188
- cvss
- 5.9
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.4%
- EPSS 1.4% chance of exploitation in 30 days, percentile 72%
- public exploits
- 0
- none known
Summary
It was found that OpenShift Container Platform versions 3.6.x - 4.6.0 does not perform SSH Host Key checking when using ssh key authentication during builds. An attacker, with the ability to redirect network traffic, could use this to alter the resulting build output.
Patch / fix
- atomic-openshift openshift 3.9 3.9.102-1.git.0.6411f52.el7
- atomic-openshift-pod openshift 3.9 3.9.102-1.git.0.6411f52.el7
- atomic-openshift-node openshift 3.9 3.9.102-1.git.0.6411f52.el7
- atomic-openshift-tests openshift 3.9 3.9.102-1.git.0.6411f52.el7
- atomic-openshift-master openshift 3.9 3.9.102-1.git.0.6411f52.el7
- atomic-openshift-clients openshift 3.9 3.9.102-1.git.0.6411f52.el7
- atomic-openshift-sdn-ovs openshift 3.9 3.9.102-1.git.0.6411f52.el7
- atomic-openshift-excluder openshift 3.9 3.9.102-1.git.0.6411f52.el7
red hat advisories RHSA-2019:3811RHSA-2019:3143RHSA-2019:2989
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2019-10150 updated cvss 5.9
atomic-openshift: OpenShift builds don't verify SSH Host Keys for the git repository
-
Red Hat OpenShift Container Platform 3.6 atomic-openshift, atomic-openshift-pod, atomic-openshift-node, atomic-openshift-tests, atomic-openshift-master, atomic-openshift-clients, +9 more Red Hat OpenShift Container Platform 3.7 atomic-openshift, atomic-openshift-pod, atomic-openshift-node, atomic-openshift-tests, atomic-openshift-master, atomic-openshift-clients, +10 moreaffected: workaround, no fix planned “Use only methods (such as HTTPS with TLS verification) that enable the identity of the remote repository to be validated.”
-
Red Hat OpenShift Container Platform 3.9 atomic-openshift 3.9.102-1.git.0.6411f52.el7, atomic-openshift-pod 3.9.102-1.git.0.6411f52.el7, atomic-openshift-node 3.9.102-1.git.0.6411f52.el7, atomic-openshift-tests 3.9.102-1.git.0.6411f52.el7, atomic-openshift-master 3.9.102-1.git.0.6411f52.el7, atomic-openshift-clients 3.9.102-1.git.0.6411f52.el7, +8 morefixed: vendor fix “Use only methods (such as HTTPS with TLS verification) that enable the identity of the remote repository to be validated.” RHSA-2019:3811
-
Red Hat OpenShift Container Platform 3.10 cri-o 1.10.6-2.rhaos3.10.git56d7d9a.el7, atomic-openshift 3.10.175-1.git.0.f9f0e81.el7, atomic-openshift-pod 3.10.175-1.git.0.f9f0e81.el7, atomic-openshift-node 3.10.175-1.git.0.f9f0e81.el7, atomic-openshift-tests 3.10.175-1.git.0.f9f0e81.el7, atomic-openshift-master 3.10.175-1.git.0.f9f0e81.el7, +8 morefixed: vendor fix “Use only methods (such as HTTPS with TLS verification) that enable the identity of the remote repository to be validated.” RHSA-2019:2989
-
Red Hat OpenShift Container Platform 3.11 atomic-openshift 3.11.153-1.git.0.aaf3f71.el7, atomic-openshift-pod 3.11.153-1.git.0.aaf3f71.el7, atomic-openshift-node 3.11.153-1.git.0.aaf3f71.el7, atomic-openshift-tests 3.11.153-1.git.0.aaf3f71.el7, atomic-openshift-master 3.11.153-1.git.0.aaf3f71.el7, atomic-openshift-clients 3.11.153-1.git.0.aaf3f71.el7, +7 morefixed: vendor fix “Use only methods (such as HTTPS with TLS verification) that enable the identity of the remote repository to be validated.” RHSA-2019:3143
-
Red Hat OpenShift Container Platform 4.1 openshift4/ose-docker-builder v4.1.20-201910102034fixed: vendor fix “Use only methods (such as HTTPS with TLS verification) that enable the identity of the remote repository to be validated.” RHSA-2019:3007
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
1.39% chance of exploitation in the next 30 days, higher than 72% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 5.9 | CVSS:3.0/AV:A/AC:H/PR:N/UI:R/S:U/C:L/I:H/A:L |
| NVD | 3.0 | 5.9 | CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N |
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:N/I:P/A:N |
Affected products
- redhat atomic-openshift
Classification
- Weakness
-
- CWE-287 Improper Authentication
References
-
access.redhat.com
/errata/RHSA-2019:2989
vendor-advisory
-
access.redhat.com
/errata/RHSA-2019:3007
vendor-advisory
-
access.redhat.com
/errata/RHSA-2019:3143
vendor-advisory
-
access.redhat.com
/errata/RHSA-2019:3811
vendor-advisory
-
docs.openshift.com
/container-platform/3.11/dev_guide/builds/build_inputs.html#source-secrets-ssh-key-authentication
vendor-advisory
-
bugzilla.redhat.com
/show_bug.cgi?id=CVE-2019-10150
issue-tracking, vendor-advisory
Sources
- CVE List CVE-2019-10150
- NVD CVE-2019-10150
Fencer Vulns 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.