Openshift Container PlatformApplication · Redhat
CVE-2019-10150
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIt 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceOpenShift Container Platform versions 3.6.x through 4.6.0 fail to perform SSH Host Key checking during builds that use SSH key authentication. This allows a man-in-the-middle attacker to intercept build traffic and inject or modify build output by impersonating the remote Git/SSH server.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Openshift Container PlatformApplication
>= 3.6, <= 4.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check OpenShift Container Platform versionRun 'oc version' or check the cluster version with 'oc get clusterversion -o yaml' to determine the installed versionAffected if Installed version is greater than or equal to 3.6 and less than or equal to 4.1
-
Identify build configurations using SSH authenticationRun 'oc get bc --all-namespaces -o jsonpath={.items[?(@.spec.source.git.secretRef.name)]}' to find build configs with git secret references, then inspect each with 'oc get bc <name> -n <namespace> -o yaml' to check if they use SSH credentialsAffected if Build configs exist that clone from git repositories using SSH credentials (secretRef pointing to an SSH key)
-
Inspect SSH known_hosts configuration in build secretsExamine the secret referenced in the build config: 'oc get secret <secret-name> -n <namespace> -o yaml' and check if it contains a 'known_hosts' data fieldAffected if The SSH secret does not contain a 'known_hosts' field or the field is empty, meaning host key verification is disabled
-
Verify build source configuration for known_hosts verificationCheck the build config spec.source.git section: 'oc get bc <name> -n <namespace> -o jsonpath={.spec.source.git}' to see if sshKnownHosts is specifiedAffected if The 'sshKnownHosts' field is absent or empty in the build source configuration, indicating strict host key checking is not enforced
You are affected if you run OpenShift version 3.6 through 4.1 and have build configurations using SSH authentication where SSH known_hosts verification is not explicitly configured.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataEnable SSH known_hosts verification in build configurations to ensure the SSH host keys are validated before establishing connections. This prevents MITM attacks during SSH-based build operations.
Fix this in Openshift Container Platform
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10150 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-10150 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data