Vulnerability Database · Go · github.com/containers/image · Version
github.com/containers/image v1.5.2-0.20190821161828-0cc0e97405db
v1.5.2-0.20190821161828-0cc0e97405db is affected by 3 vulnerabilities.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to. The upgrade Vulert recommends: v3.0.2+incompatible.
Critical 0 High 1 Medium 1 Low 0 Unrated 1
-
Released 21 Aug 2019
Licence Apache-2.0
Also known from other sources 3
Newer releases 300
Database updated 23/Oct/2026
Release and licence data published by the Go module proxy. Licence information is not legal advice.
Concerned about your application's security?
Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.
01 Vulnerabilities affecting this version
github.com/containers/image v1.5.2-0.20190821161828-0cc0e97405db vulnerabilities
3 vulnerabilities cover github.com/containers/image v1.5.2-0.20190821161828-0cc0e97405db. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| Unexpected Authenticated Registry Access in github.com/containers/image | 8.3 high | 5.30.1 | 14 May 2024 |
| CVE-2019-10214: Insufficiently Protected Credentials in containers/image | 6.4 medium | 3.0.0 | 15 Feb 2022 |
| CVE-2019-10214: Insufficiently Protected Credentials in github.com/containers/image | N/A unrated | 2.0.2-0.20190802080134-634605d06e73+incompatible | 14 Apr 2021 |
Looking for another version, or everything Vulert holds for github.com/containers/image?
Questions
About github.com/containers/image v1.5.2-0.20190821161828-0cc0e97405db
Is github.com/containers/image v1.5.2-0.20190821161828-0cc0e97405db vulnerable?
Yes. 3 vulnerabilities in the Vulert database cover github.com/containers/image v1.5.2-0.20190821161828-0cc0e97405db: 0 critical, 1 high, 1 medium and 0 low, plus 1 not yet rated. The upgrade Vulert recommends is v3.0.2+incompatible, and each entry above names the fixed version to move to.
Which version of github.com/containers/image should I use instead of v1.5.2-0.20190821161828-0cc0e97405db?
v3.0.2+incompatible is the version Vulert recommends for this release line. The version table on the package page lists every release with the vulnerabilities recorded against it.
Is v1.5.2-0.20190821161828-0cc0e97405db the latest release of github.com/containers/image?
No. v1.5.2-0.20190821161828-0cc0e97405db was published 21 Aug 2019, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.
How do I monitor github.com/containers/image for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/containers/image version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.