Libcontainer vulnerabilitiesRanked by how likely they are to be used.
Libcontainer is made by Docker. We track 2 published vulnerabilities in it, across 1 version. None of them is on the list of flaws known to be exploited today. If you run Libcontainer, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Libcontainer vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Libcontainer's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Libcontainer flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 0.6%CVE-2015-3627High
Libcontainer and Docker Engine before 1.6.1 opens the file-descriptor passed to the pid-1 process before performing the chroot, which allows local users to gain privileges via a symlink attack in an image.
- 0.6%CVE-2015-3629High
Libcontainer 1.6.0, as used in Docker Engine, allows local users to escape containerization ("mount namespace breakout") and write to arbitrary file on the host system via a symlink attack in an image when respawning...
Running Libcontainer? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
Libcontainer and Docker Engine before 1.6.1 opens the file-descriptor passed to the pid-1 process before performing the chroot, which allows local users to gain privileges via a symlink attack in an image.
- Matched to
- Libcontainer on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 2 published vulnerabilities listed under the name Libcontainer, across 1 version.
None of Libcontainer's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Libcontainer. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.