OpenshiftApplication · Redhat
CVE-2019-14845
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 · uneditedA vulnerability was found in OpenShift builds, versions 4.1 up to 4.3. Builds that extract source from a container image, bypass the TLS hostname verification. An attacker can take advantage of this flaw by launching a man-in-the-middle attack and injecting malicious content.
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 · moderate confidenceIn OpenShift versions 4.1 through 4.3, build processes that extract source code from container images fail to perform TLS hostname verification. While TLS encryption may be established, the hostname is not validated against the certificate, enabling an attacker positioned on the network path to perform a man-in-the-middle attack and inject malicious content into the build process.
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
OpenshiftApplication
>= 4.1, <= 4.3CVSS 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
- Adjacent
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:A/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 cluster versionRun 'oc get clusterversion' or 'oc version' to identify the installed OpenShift version numberAffected if Version is 4.1, 4.2, or 4.3 (any version >= 4.1 and <= 4.3)
-
Identify builds using container image sourcesRun 'oc get buildconfigs --all-namespaces' to list all BuildConfig resources, then inspect each with 'oc get buildconfig <name> -n <namespace> -o yaml' to check the 'spec.source.type' fieldAffected if Any BuildConfig has 'source.type' set to 'Image' or references an ImageStreamTag or DockerImage as the source
-
Check for source pull secrets using external registriesExamine BuildConfigs for 'spec.source.pullSecret' entries that reference external container registries (not internal ImageStream secrets). Use 'oc get buildconfig <name> -n <namespace> -o jsonpath={.spec.source.pullSecret}'Affected if Builds pull source images from external registries using secrets configured for those registries
-
Verify TLS certificate validation is enforcedReview build logs or build pod specifications for evidence of TLS hostname verification. Check if the build process uses a transport that validates hostnames when pulling container imagesAffected if No explicit TLS hostname verification is configured or the build uses a transport that skips hostname validation for image pulls
You are affected if your OpenShift version is 4.1, 4.2, or 4.3 AND you have builds configured to use container images as source from any registry.
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 dataUpgrade to OpenShift 4.4 or later, or ensure builds using container image sources are configured to enforce proper TLS hostname verification to prevent MITM attacks.
Fix this in Openshift
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-14845 — 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-14845 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