Security readout for executives and security teams
Plain-English summary
This issue lets someone with Docker container access cause host-side data loss on certain older Linux kernels because Docker Moby did not block a sensitive /proc/scsi path. It is not described as data theft or remote takeover, but availability impact can be serious where vulnerable Docker and kernel conditions exist.
Executive priority
Treat this as a legacy-container availability risk. It does not justify emergency response absent affected hosts, but organizations with old Docker infrastructure should validate quickly because the potential impact is host data loss or service disruption.
Technical view
Docker Moby through 17.03.2-ce generated a default Linux OCI spec that did not block /proc/scsi pathnames. The CVE describes availability impact from container access to /proc/scsi/scsi on older kernels. Public references include Moby PR #35399 and a related commit; the source bundle does not name a fixed release.
Likely exposure
Likely exposure is legacy Docker Moby deployments at or before 17.03.2-ce, especially on older Linux kernels where /proc/scsi behavior can affect storage devices. Modern container platforms may be unaffected, but validation should focus on old hosts and untrusted or multi-tenant container workloads.
Exploitation context
The source bundle does not show active exploitation, and the CVE is not in KEV. Exploitation requires specific environmental conditions and container access. The public description identifies the sensitive target path and impact, but does not provide evidence of widespread abuse.
Researcher notes
The CVE maps to CWE-200, though the described impact is availability loss through insufficient path blocking. Evidence is strongest for the vulnerable condition and Moby fix discussion; the provided sources do not establish active exploitation or a specific patched release.
Mitigation direction
- Upgrade Docker Moby to a release that includes the /proc/scsi blocklist change.
- Review Moby PR #35399 and vendor advisories for the exact fixed version.
- Retire or update older Linux kernels on Docker hosts where feasible.
- Avoid running untrusted containers on legacy Docker hosts.
- Apply defense-in-depth controls limiting container access to host proc paths.
Validation and detection
- Inventory Docker Moby versions and flag hosts running through 17.03.2-ce.
- Identify Docker hosts using older Linux kernels.
- Confirm the runtime default spec blocks /proc/scsi pathnames.
- Review whether untrusted users can launch containers on flagged hosts.
- Prioritize systems where storage availability is business-critical.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-200: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupContainer behavior lookup
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2017-16539 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.9 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H2.23.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.9MediumVector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://marc.info/?l=linux-scsi&m=150985455801444&w=2CVE reference · x_refsource_MISC
- https://github.com/moby/moby/pull/35399/commits/a21ecdf3c8a343a7c94e4c4d01b178c87ca7aaa1CVE reference · x_refsource_MISC
- https://marc.info/?l=linux-scsi&m=150985062200941&w=2CVE reference · x_refsource_MISC
- https://github.com/moby/moby/pull/35399CVE reference · x_refsource_MISC
- https://twitter.com/ewindisch/status/926443521820774401CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Exposure of Sensitive Information to an Unauthorized Actor
Exposure of Sensitive Information to an Unauthorized Actor represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.