CVE-2019-10214: Insufficiently Protected Credentials in containers/image

github.com/containers/image Updated 02 Oct 2025

Summary

15/02/2022
Yes i
Moderate
6.4

CVE-2019-10214: containers/image library Insufficiently Protects Credentials. Affects github.com/containers/image versions < 3.0.0. Fixed in 3.0.0. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The containers/image library is utilized by container tools such as Podman, Buildah, and Skopeo in Red Hat Enterprise Linux version 8, as well as CRI-O in OpenShift Container Platform. This library is responsible for managing container images and interacting with container registries. It is implemented in Go and can be accessed via the 'github.com/containers/image' package.

Vulnerability Detail

The vulnerability identified as CVE-2019-10214 involves insufficiently protected credentials within the containers/image library. Specifically, the library does not enforce TLS connections to the container registry authorization service. This flaw opens up the possibility of a Man-in-the-Middle (MitM) attack, where an attacker can intercept network traffic and steal login credentials or bearer tokens. The impact of this vulnerability could be significant, as unauthorized access to container registries can lead to the compromise of sensitive data and the execution of unauthorized actions.

How To Fix

Latest published version: v3.0.2+incompatible as of 23 Oct 2026

go get github.com/containers/image@v3.0.2+incompatible

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

3.0.0

This is the first release that contains the fix.

go get github.com/containers/image@v3.0.0

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no specific workaround mentioned for this vulnerability. However, as a general security practice, it is advisable to ensure that container registries are accessed over secure connections (HTTPS) and to regularly monitor network traffic for any suspicious activity.

Conclusion

In conclusion, the CVE-2019-10214 vulnerability in the containers/image library exposes credentials to potential theft through a lack of TLS enforcement. To mitigate this vulnerability, it is crucial to update the library to version 3.0.0 or later and ensure secure connections to container registries. Regular monitoring of network traffic is also recommended to detect any suspicious activity. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for github.com/containers/image →

Share this vulnerability

FAQ

The vulnerability allows an attacker to perform a Man-in-the-Middle attack and steal login credentials or bearer tokens. This can lead to unauthorized access to container registries and potential compromise of sensitive data.

The vulnerability affects container tools such as Podman, Buildah, Skopeo, and CRI-O, which utilize the containers/image library.

Yes, updating the containers/image library to version 3.0.0 or later resolves this vulnerability.

While there are no specific mitigations mentioned, it is recommended to ensure secure connections (HTTPS) to container registries and monitor network traffic for any suspicious activity.

Related vulnerabilities

Recent vulnerabilities recorded for github.com/containers/image.

How To Fix

Latest published version: v3.0.2+incompatible as of 23 Oct 2026

go get github.com/containers/image@v3.0.2+incompatible

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

3.0.0

This is the first release that contains the fix.

go get github.com/containers/image@v3.0.0

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback