# CVE-2017-16539: Docker Moby /proc/scsi Path Exposure Allows Host Data Loss (SCSI MICDROP)

> Attackers with container access can write to /proc/scsi to trigger SCSI device removal, causing data loss or denial of service on vulnerable Linux kernels.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 Nov 2017
- **Updated:** 27 Jan 2026
- **Also known as:** DEBIAN-CVE-2017-16539, GHSA-vfjc-2qcw-j95j, UBUNTU-CVE-2017-16539

## What is CVE-2017-16539?

CVE-2017-16539 is a medium-severity missing authorization vulnerability in n/a, published on 4 Nov 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2017-16539?

2 open source packages ship an affected version, including github.com/moby/moby. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/moby/moby` | Go | All versions | 17.12.0-ce |
| `github.com/moby/moby` | Go | All versions | 17.12.0-ce |

Products: Mobyproject Moby.

## How do I fix CVE-2017-16539?

Upgrade github.com/moby/moby to 17.12.0-ce or later.

## Is CVE-2017-16539 being exploited?

There is no known exploitation of CVE-2017-16539 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2024-36623](https://insights.sbomify.com/CVE-2024-36623/): Moby Race Condition vulnerability (high 8.1)
- [CVE-2023-28840](https://insights.sbomify.com/CVE-2023-28840/): moby/moby's dockerd daemon encrypted overlay network may be unauthenticated (high 7.5)
- [CVE-2018-12608](https://insights.sbomify.com/CVE-2018-12608/): Docker Authentication Bypass (high 7.5)
- [CVE-2024-24557](https://insights.sbomify.com/CVE-2024-24557/): Moby classic builder cache poisoning (medium 6.9)
- [CVE-2023-28841](https://insights.sbomify.com/CVE-2023-28841/): moby/moby's dockerd daemon encrypted overlay network traffic may be unencrypted (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-16539 and fix it if it is affected.

What it is: CVE-2017-16539 is a medium-severity missing authorization vulnerability in n/a, published on 4 Nov 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-16539 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/moby/moby (Go): affected all versions; fixed in 17.12.0-ce
- github.com/moby/moby (Go): affected all versions; fixed in 17.12.0-ce

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-16539/ (Markdown: https://insights.sbomify.com/CVE-2017-16539/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-16539
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-16539
- OSV: https://osv.dev/vulnerability/CVE-2017-16539

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-16539/
Summaries are generated and may contain mistakes; the official description above is the record.