# CVE-2019-10214: containers/image library Insufficiently Protects Credentials > Attackers can intercept unencrypted registry auth traffic to steal credentials or tokens via Man-in-the-Middle attacks. - **Severity:** Medium 6.4 (`CVSS:3.0/AV:A/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Local or same network only - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 25 Nov 2019 - **Updated:** 4 Aug 2024 - **Also known as:** GHSA-85p9-j7c9-v4gr, GO-2021-0081, RHSA-2019:2825, RHSA-2019:3812, SUSE-SU-2019:2340-1, SUSE-SU-2019:2341-1, SUSE-SU-2019:2346-1, SUSE-SU-2020:0712-1, UBUNTU-CVE-2019-10214, openSUSE-SU-2019:2137-1, openSUSE-SU-2019:2138-1, openSUSE-SU-2019:2143-1, openSUSE-SU-2019:2159-1, openSUSE-SU-2020:0377-1 ## What is CVE-2019-10214? CVE-2019-10214 is a medium-severity vulnerability in Opensuse Leap, published on 25 Nov 2019. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. ### Official description The containers/image library used by the container tools Podman, Buildah, and Skopeo in Red Hat Enterprise Linux version 8 and CRI-O in OpenShift Container Platform, does not enforce TLS connections to the container registry authorization service. An attacker could use this vulnerability to launch a MiTM attack and steal login credentials or bearer tokens. Weakness: CWE-522 (Insufficiently Protected Credentials) ## Which versions are affected by CVE-2019-10214? 3 open source packages ship an affected version, including github.com/containers/image. It affects 6 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/containers/image` | Go | All versions | 2.0.2-0.20190802080134-634605d06e73+incompatible | | `github.com/containers/image` | Go | All versions | 3.0.0 | | `github.com/containers/image` | Go | All versions | 3.0.0 | | `cri-o` | Red Hat:openshift:3.9::el7 | All versions | 0:1.9.16-5.git858756d.el7 | | `cri-o-debuginfo` | Red Hat:openshift:3.9::el7 | All versions | 0:1.9.16-5.git858756d.el7 | | `cri-o` | Red Hat:openshift:4.1::el7 | All versions | 0:1.13.11-0.4.dev.rhaos4.1.git9cb8f2f.el7 | | `cri-o-debuginfo` | Red Hat:openshift:4.1::el7 | All versions | 0:1.13.11-0.4.dev.rhaos4.1.git9cb8f2f.el7 | | `cri-o` | Red Hat:openshift:4.1::el8 | All versions | 0:1.13.11-0.7.dev.rhaos4.1.git9cb8f2f.el8 | | `cri-o-debuginfo` | Red Hat:openshift:4.1::el8 | All versions | 0:1.13.11-0.7.dev.rhaos4.1.git9cb8f2f.el8 | | `cri-o-debugsource` | Red Hat:openshift:4.1::el8 | All versions | 0:1.13.11-0.7.dev.rhaos4.1.git9cb8f2f.el8 | | `buildah` | SUSE:Linux Enterprise Module for Containers 15 SP1 | All versions | 1.7.1-3.3.1 | | `podman` | SUSE:Linux Enterprise Module for Containers 15 SP1 | All versions | 1.4.4-4.11.1 | | `skopeo` | SUSE:Linux Enterprise Module for Server Applications 15 | All versions | 0.1.32-4.8.1 | | `skopeo` | SUSE:Linux Enterprise Module for Server Applications 15 SP1 | All versions | 0.1.32-4.8.1 | | `skopeo` | SUSE:Linux Enterprise Module for Server Applications 15 SP1 | All versions | 0.1.41-4.11.1 | | `skopeo` | openSUSE:Leap 15.0 | All versions | 0.1.32-lp150.8.1 | | `buildah` | openSUSE:Leap 15.1 | All versions | 1.7.1-lp151.2.3.1 | | `podman` | openSUSE:Leap 15.1 | All versions | 1.4.4-lp151.3.6.1 | | `skopeo` | openSUSE:Leap 15.1 | All versions | 0.1.32-lp151.2.3.1 | | `skopeo` | openSUSE:Leap 15.1 | All versions | 0.1.41-lp151.2.6.1 | Products: Buildah Project Buildah, Libpod Project Libpod, Opensuse Leap, Redhat Enterprise Linux, Redhat Openshift Container Platform, Skopeo Project Skopeo. ## How do I fix CVE-2019-10214? Upgrade github.com/containers/image to a fixed version for your release line: 2.0.2-0.20190802080134-634605d06e73+incompatible or 3.0.0. ## Is CVE-2019-10214 being exploited? There is no known exploitation of CVE-2019-10214 in the wild and no public exploit code. ## Other vulnerabilities in Opensuse Leap - [CVE-2020-10696](https://insights.sbomify.com/CVE-2020-10696/): Path Traversal in Buildah (high 8.8) - [CVE-2024-9675](https://insights.sbomify.com/CVE-2024-9675/): Buildah: buildah allows arbitrary directory mount (high 7.8) - [CVE-2022-2990](https://insights.sbomify.com/CVE-2022-2990/): Buildah's incorrect handling of the supplementary groups may lead to data disclosure, modification (high 7.1) - [CVE-2022-27651](https://insights.sbomify.com/CVE-2022-27651/): Non-empty default inheritable capabilities for linux container in Buildah (medium 6.8) - [CVE-2021-3602](https://insights.sbomify.com/CVE-2021-3602/): Buildah processes using chroot isolation may leak environment values to intermediate processes (medium 5.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2019-10214 and fix it if it is affected. What it is: CVE-2019-10214 is a medium-severity vulnerability in Opensuse Leap, published on 25 Nov 2019. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2019-10214 in the wild and no public exploit code. Affected packages and fixed versions: - github.com/containers/image (Go): affected all versions; fixed in 2.0.2-0.20190802080134-634605d06e73+incompatible - github.com/containers/image (Go): affected all versions; fixed in 3.0.0 - github.com/containers/image (Go): affected all versions; fixed in 3.0.0 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2019-10214/ (Markdown: https://insights.sbomify.com/CVE-2019-10214/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2019-10214 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-10214 - OSV: https://osv.dev/vulnerability/CVE-2019-10214 --- From sbomify Insights: https://insights.sbomify.com/CVE-2019-10214/ Summaries are generated and may contain mistakes; the official description above is the record.