Docker before 1.3 does not properly validate image IDs, which allows remote attackers to redirect to another image through the loading of untrusted images via 'docker load'.
| Product | Vendor Advisory | Solution File | Added | Published |
|---|---|---|---|---|
| Debian | — | Upgrade docker.io | Jul 30, 2024 | Feb 6, 2018 |
| Docker | — | Upgrade to Docker v1.3 | Apr 27, 2018 | Feb 6, 2018 |
| Echo Linux | — | Upgrade docker.io | Nov 12, 2026 | Feb 6, 2018 |
| Redhat_linux | — | No solution exists | Jul 9, 2025 | Feb 6, 2018 |
| Suse | — | Upgrade sle2dockerUpgrade ruby2.1-rubygem-sle2dockerUpgrade docker | Dec 18, 2015 | Dec 15, 2014 |
With curated Threat Intelligence, you can see which vulnerabilities truly put you at risk, prioritize what matters most, and act before attackers do.
Explore Intelligence Hub