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 authenticati
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.
- Published
- Jun 12, 2019
- Updated
- Jun 16, 2026
- EPSS
- 1.4% · 71th percentile
- CWE
- CWE-287
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
23
Monitor
Low priority for now.
- CVSS
- 23 / 40 · 5.9 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.4%
CNA vs NVD score
- NVD
- 5.9
- CNA · redhat
- 5.9
- agree
CVSS:3.0/AV:A/AC:H/PR:N/UI:R/S:U/C:L/I:H/A:L
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| redhat | openshift container platform | cpe:2.3:a:redhat:openshift_container_platform |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- redhat openshift container platform3.6 and later · up to 4.1 inclusive
Versions reported by the vendor
Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.
redhat atomic-openshift
- 3.6.x - 4.0.0affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Red Hat:openshift:3.10::el7 | atomic-openshift | before 0:3.10.175-1.git.0.f9f0e81.el7 | 0:3.10.175-1.git.0.f9f0e81.el7 |
| Red Hat:openshift:3.10::el7 | atomic-openshift-clients | before 0:3.10.175-1.git.0.f9f0e81.el7 | 0:3.10.175-1.git.0.f9f0e81.el7 |
| Red Hat:openshift:3.10::el7 | atomic-openshift-clients-redistributable | before 0:3.10.175-1.git.0.f9f0e81.el7 | 0:3.10.175-1.git.0.f9f0e81.el7 |
| Red Hat:openshift:3.10::el7 | atomic-openshift-docker-excluder | before 0:3.10.175-1.git.0.f9f0e81.el7 | 0:3.10.175-1.git.0.f9f0e81.el7 |
| Red Hat:openshift:3.10::el7 | atomic-openshift-excluder | before 0:3.10.175-1.git.0.f9f0e81.el7 | 0:3.10.175-1.git.0.f9f0e81.el7 |
| Red Hat:openshift:3.10::el7 | atomic-openshift-hyperkube | before 0:3.10.175-1.git.0.f9f0e81.el7 | 0:3.10.175-1.git.0.f9f0e81.el7 |
| Red Hat:openshift:3.10::el7 | atomic-openshift-hypershift | before 0:3.10.175-1.git.0.f9f0e81.el7 | 0:3.10.175-1.git.0.f9f0e81.el7 |
| Red Hat:openshift:3.10::el7 | atomic-openshift-master | before 0:3.10.175-1.git.0.f9f0e81.el7 | 0:3.10.175-1.git.0.f9f0e81.el7 |
| Red Hat:openshift:3.10::el7 | atomic-openshift-node | before 0:3.10.175-1.git.0.f9f0e81.el7 | 0:3.10.175-1.git.0.f9f0e81.el7 |
| Red Hat:openshift:3.10::el7 | atomic-openshift-pod | before 0:3.10.175-1.git.0.f9f0e81.el7 | 0:3.10.175-1.git.0.f9f0e81.el7 |
| Red Hat:openshift:3.10::el7 | atomic-openshift-sdn-ovs | before 0:3.10.175-1.git.0.f9f0e81.el7 | 0:3.10.175-1.git.0.f9f0e81.el7 |
| Red Hat:openshift:3.10::el7 | atomic-openshift-template-service-broker | before 0:3.10.175-1.git.0.f9f0e81.el7 | 0:3.10.175-1.git.0.f9f0e81.el7 |
| Red Hat:openshift:3.10::el7 | atomic-openshift-tests | before 0:3.10.175-1.git.0.f9f0e81.el7 | 0:3.10.175-1.git.0.f9f0e81.el7 |
| Red Hat:openshift:3.10::el7 | cri-o | before 0:1.10.6-2.rhaos3.10.git56d7d9a.el7 | 0:1.10.6-2.rhaos3.10.git56d7d9a.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift | before 0:3.11.153-1.git.0.aaf3f71.el7 | 0:3.11.153-1.git.0.aaf3f71.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-clients | before 0:3.11.153-1.git.0.aaf3f71.el7 | 0:3.11.153-1.git.0.aaf3f71.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-clients-redistributable | before 0:3.11.153-1.git.0.aaf3f71.el7 | 0:3.11.153-1.git.0.aaf3f71.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-docker-excluder | before 0:3.11.153-1.git.0.aaf3f71.el7 | 0:3.11.153-1.git.0.aaf3f71.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-excluder | before 0:3.11.153-1.git.0.aaf3f71.el7 | 0:3.11.153-1.git.0.aaf3f71.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-hyperkube | before 0:3.11.153-1.git.0.aaf3f71.el7 | 0:3.11.153-1.git.0.aaf3f71.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-hypershift | before 0:3.11.153-1.git.0.aaf3f71.el7 | 0:3.11.153-1.git.0.aaf3f71.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-master | before 0:3.11.153-1.git.0.aaf3f71.el7 | 0:3.11.153-1.git.0.aaf3f71.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-node | before 0:3.11.153-1.git.0.aaf3f71.el7 | 0:3.11.153-1.git.0.aaf3f71.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-pod | before 0:3.11.153-1.git.0.aaf3f71.el7 | 0:3.11.153-1.git.0.aaf3f71.el7 |
+17
Same product
redhat: all recordsOther highest-scoring records for the same primary product.
- CVE-2017-7481Ansible before versions 2.3.1.0 and 2.4.0.0 fails to properly mark lookup-plugin results as unsafe.40Plan
- CVE-2018-1085openshift-ansible before versions 3.9.23, 3.7.46 deploys a misconfigured etcd file that causes the SSL client certificate authentication to 40Plan
- CVE-2020-27836A flaw was found in cluster-ingress-operator.39Monitor
- CVE-2019-3899It was found that default configuration of Heketi does not require any authentication potentially exposing the management interface to misus39Monitor
- CVE-2026-54099Windows-machine-config-operator: windows-machine-config-operator: wicd csr extra-organization allows privilege escalation to system:masters35Monitor
- CVE-2026-1784Ose-cluster-ingress-operator: remote code execution through haproxy configuration injection35Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| red hat:atomic-openshift | 0:3.10.175-1.git.0.f9f0e81.el7 · Red Hat:openshift:3.10::el7 | Package registry (OSV) |
| red hat:atomic-openshift-clients | 0:3.10.175-1.git.0.f9f0e81.el7 · Red Hat:openshift:3.10::el7 | Package registry (OSV) |
| red hat:atomic-openshift-clients-redistributable | 0:3.10.175-1.git.0.f9f0e81.el7 · Red Hat:openshift:3.10::el7 | Package registry (OSV) |
| red hat:atomic-openshift-docker-excluder | 0:3.10.175-1.git.0.f9f0e81.el7 · Red Hat:openshift:3.10::el7 | Package registry (OSV) |
| red hat:atomic-openshift-excluder | 0:3.10.175-1.git.0.f9f0e81.el7 · Red Hat:openshift:3.10::el7 | Package registry (OSV) |
| red hat:atomic-openshift-hyperkube | 0:3.10.175-1.git.0.f9f0e81.el7 · Red Hat:openshift:3.10::el7 | Package registry (OSV) |
| red hat:atomic-openshift-hypershift | 0:3.10.175-1.git.0.f9f0e81.el7 · Red Hat:openshift:3.10::el7 | Package registry (OSV) |
| red hat:atomic-openshift-master | 0:3.10.175-1.git.0.f9f0e81.el7 · Red Hat:openshift:3.10::el7 | Package registry (OSV) |
| red hat:atomic-openshift-node | 0:3.10.175-1.git.0.f9f0e81.el7 · Red Hat:openshift:3.10::el7 | Package registry (OSV) |
| red hat:atomic-openshift-pod | 0:3.10.175-1.git.0.f9f0e81.el7 · Red Hat:openshift:3.10::el7 | Package registry (OSV) |
| red hat:atomic-openshift-sdn-ovs | 0:3.10.175-1.git.0.f9f0e81.el7 · Red Hat:openshift:3.10::el7 | Package registry (OSV) |
| red hat:atomic-openshift-template-service-broker | 0:3.10.175-1.git.0.f9f0e81.el7 · Red Hat:openshift:3.10::el7 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- none
- Integrity
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
CWE-287 · Improper AuthenticationCVSS vector
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
nvd-primary
Root cause
Authentication is added route by route instead of being enforced in one place. When a route added later bypasses the shared middleware, the session check never runs for it.
The bug in code
The whole CWE-287 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
app.use("/admin", requireSession, adminRouter);
// Route added later skips the middlewareapp.post("/admin-api/config", updateConfig);Fixed
const admin = express.Router();admin.use(requireSession, requireRole("admin"));
admin.post("/config", updateConfig);app.use("/admin", admin);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Authentication AbuseCAPEC-114Medium
- Authentication BypassCAPEC-115Medium
- Identity SpoofingCAPEC-151likelihood: Medium · Medium
- Fake the Source of DataCAPEC-194Medium
- Exploiting Trust in ClientCAPEC-22likelihood: High · High
- Utilizing REST's Trust in the System Resource to Obtain Sensitive DataCAPEC-57likelihood: Medium · Very High
- Session HijackingCAPEC-593likelihood: High · Very High
- Token ImpersonationCAPEC-633Medium
ATT&CK techniques
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- access.redhat.com/errata/RHSA-2019:3007
- access.redhat.com/errata/RHSA-2019:3143
- access.redhat.com/errata/RHSA-2019:3811
- access.redhat.com/errata/RHSA-2019:2989
- bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-10150
- docs.openshift.com/container-platform/3.11/dev_guide/builds/build_inputs.html#source-secrets-ssh-key-authentication
Vendor advisories and official records. Exploit/PoC links are deliberately left out.