Information Exposure Affecting docker.io package, versions <1.13.1~ds3-1
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-DEBIANUNSTABLE-DOCKERIO-301844
- published4 Nov 2017
- disclosed4 Nov 2017
Introduced: 4 Nov 2017
CVE-2017-16539 (opens in a new tab)How to fix?
Upgrade Debian:unstable docker.io to version 1.13.1~ds3-1 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream docker.io package and not the docker.io package as distributed by Debian.
See How to fix? for Debian:unstable relevant fixed versions and status.
The DefaultLinuxSpec function in oci/defaults.go in Docker Moby through 17.03.2-ce does not block /proc/scsi pathnames, which allows attackers to trigger data loss (when certain older Linux kernels are used) by leveraging Docker container access to write a "scsi remove-single-device" line to /proc/scsi/scsi, aka SCSI MICDROP.
References
- https://security-tracker.debian.org/tracker/CVE-2017-16539
- https://github.com/moby/moby/pull/35399/commits/a21ecdf3c8a343a7c94e4c4d01b178c87ca7aaa1
- https://github.com/moby/moby/pull/35399
- https://marc.info/?l=linux-scsi&m=150985062200941&w=2
- https://marc.info/?l=linux-scsi&m=150985455801444&w=2
- https://twitter.com/ewindisch/status/926443521820774401
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2017-16539